App Actions pattern in Cypress - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the App Actions pattern in Cypress testing?

It is a way to organize test code by grouping user actions (like clicks, typing) into reusable functions. This makes tests easier to read and maintain.

beginner

Why should you use the App Actions pattern?

Because it helps avoid repeating code, makes tests clearer, and lets you update actions in one place if the app changes.

beginner

How do you define an action in the App Actions pattern?

You write a function that performs a user step, like clicking a button or filling a form field, using Cypress commands inside.

beginner

Example: What does this action do?<br><pre>function login(username, password) {<br>  cy.get('#user').type(username);<br>  cy.get('#pass').type(password);<br>  cy.get('#login-btn').click();<br>}</pre>

This action types the username and password into input fields and clicks the login button, simulating a user login.

beginner

How does the App Actions pattern improve test readability?

Tests read like a story because actions have clear names, so you understand what the test does without seeing all the low-level commands.

What is the main benefit of using the App Actions pattern in Cypress?

A It removes the need for assertions.

B It makes tests run faster.

C It automatically generates test data.

D It groups user steps into reusable functions.

The App Actions pattern groups user steps into reusable functions to improve code reuse and clarity.

Which of these is a good example of an App Action?

A function submitForm() { cy.get('#submit').click() }

B cy.get('#submit').click()

C assert.equal(2 + 2, 4)

D describe('Test suite', () => {})

An App Action is a function that wraps user steps, like clicking a button.

How does the App Actions pattern help when the app UI changes?

A You update the action functions in one place.

B It prevents UI changes.

C It automatically fixes selectors.

D You rewrite all tests from scratch.

Updating action functions in one place keeps tests working without rewriting them all.

What should an App Action function NOT include?

A User interaction steps like clicks and typing.

B Cypress commands like cy.get().

C Assertions to check results.

D Clear, descriptive function names.

App Actions focus on user steps; assertions belong in test cases.

Which naming style is best for App Actions?

A doStuff()

B loginUser()

C test1()

D click()

Clear, descriptive names like loginUser() explain what the action does.

Explain the App Actions pattern and why it is useful in Cypress testing.

Think about how you can avoid repeating code in tests.

Describe how you would create and use an App Action for logging into a web app.

Imagine the steps a user takes to log in.

Practice

1. What is the main benefit of using the App Actions pattern in Cypress tests?

easy

A. It automatically generates test data for each test run.

B. It speeds up test execution by running tests in parallel.

C. It replaces the need for assertions in tests.

D. It groups test steps into reusable methods to keep tests clean and maintainable.

Solution

1. Step 1: Understand the purpose of App Actions pattern

   The pattern groups common test steps into reusable methods to avoid repetition.

2. Step 2: Identify the benefit in test code

   This grouping makes tests cleaner and easier to maintain by reusing code.

3. Final Answer:

   It groups test steps into reusable methods to keep tests clean and maintainable. -> Option D

4. Quick Check:

   Reusable methods = cleaner tests [OK]

Hint: Remember: App Actions = reusable test steps [OK]

Common Mistakes:

• Thinking App Actions generate test data automatically
• Confusing App Actions with test assertions
• Assuming App Actions speed up test execution

2. Which of the following is the correct way to define an App Action method for logging in a user in Cypress?

easy

A. const login = () => { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); }

B. cy.login = () => { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); }

C. function login() { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); }

D. login() { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); }

Solution

1. Step 1: Identify valid JavaScript function syntax

   const login = () => { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); } uses a valid arrow function assigned to a constant, which is common in Cypress helper files.

2. Step 2: Check other options for syntax errors

   function login() { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); } is a function declaration but not exported or assigned; cy.login = () => { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); } incorrectly assigns to cy object; login() { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); } is invalid syntax.

3. Final Answer:

   const login = () => { cy.get('#user').type('admin'); cy.get('#pass').type('1234'); cy.get('#submit').click(); } -> Option A

4. Quick Check:

   Arrow function assigned to const = correct syntax [OK]

Hint: Use arrow functions assigned to const for App Actions [OK]

Common Mistakes:

• Using invalid function syntax without const or arrow
• Attaching methods directly to cy object incorrectly
• Omitting function keyword or arrow in definitions

3. Given this App Action method:

const addItem = (name) => { cy.get('#item-input').type(name); cy.get('#add-button').click(); }

What will be the result of this test code?

addItem('Book'); cy.get('#item-list').should('contain', 'Book');

medium

A. The test will fail because addItem does not return a value.

B. The test will pass if 'Book' appears in the item list after adding.

C. The test will throw a syntax error due to missing return statement.

D. The test will pass only if the input field has a placeholder 'Book'.

Solution

1. Step 1: Understand what addItem does

   It types the given name into the input and clicks the add button, triggering UI update.

2. Step 2: Analyze the assertion

   The test checks if '#item-list' contains the text 'Book', which should be true after adding.

3. Final Answer:

   The test will pass if 'Book' appears in the item list after adding. -> Option B

4. Quick Check:

   UI updates with added item = test passes [OK]

Hint: Add item then check list contains it [OK]

Common Mistakes:

• Assuming missing return causes failure
• Confusing input placeholder with typed value
• Expecting addItem to return a value

4. This App Action method is intended to log in a user:

const login = (user, pass) => { cy.get('#username').type(user); cy.get('#password').type(pass); cy.get('#login-btn').click }

What is the error and how to fix it?

medium

A. Missing parentheses after click; fix by changing to cy.get('#login-btn').click().

B. Wrong selector for username; fix by using #user instead of #username.

C. Missing return statement; fix by adding return before cy commands.

D. Using arrow function incorrectly; fix by using function keyword.

Solution

1. Step 1: Check method chaining syntax

   The click command is missing parentheses, so it is not called.

2. Step 2: Fix the click command

   Add parentheses to call the function: click() to perform the click action.

3. Final Answer:

   Missing parentheses after click; fix by changing to cy.get('#login-btn').click() -> Option A

4. Quick Check:

   Method calls need parentheses [OK]

Hint: Always add () to call Cypress commands like click [OK]

Common Mistakes:

• Forgetting parentheses on Cypress commands
• Changing selectors without verifying correctness
• Thinking return is needed for Cypress commands

5. You want to create an App Action to add multiple items from an array and verify all appear in the list. Which is the best approach?

hard

A. Use a single cy.get() call to type all items at once separated by commas.

B. Write separate tests for each item instead of looping in one method.

C. Create an addItems method that loops over the array, calls addItem for each, then asserts all items appear.

D. Add all items by typing them in one input, then click add once.

Solution

1. Step 1: Understand the need for reusability and verification

   Looping over the array and calling addItem reuses existing code and ensures each item is added properly.

2. Step 2: Verify all items appear after adding

   After adding, asserting all items appear confirms the UI updated correctly for each item.

3. Final Answer:

   Create an addItems method that loops over the array, calls addItem for each, then asserts all items appear. -> Option C

4. Quick Check:

   Loop + reuse + verify = best practice [OK]

Hint: Loop array, reuse addItem, then assert all present [OK]

Common Mistakes:

• Typing all items at once without separate adds
• Writing many separate tests instead of one reusable method
• Assuming one click adds multiple items automatically