Responsive breakpoint testing in Cypress - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is responsive breakpoint testing?

It is testing a website or app at different screen sizes to make sure it looks and works well on all devices like phones, tablets, and desktops.

beginner

Why do we test at different breakpoints?

Because websites change layout and style at certain screen widths called breakpoints, testing ensures the site stays usable and pretty on all devices.

intermediate

How can Cypress help with responsive breakpoint testing?

Cypress can set the browser size to different widths and heights during tests, so you can check how your site behaves at each breakpoint automatically.

beginner

Example of setting viewport size in Cypress?

Use cy.viewport(width, height) to change the browser size. For example, cy.viewport(375, 667) sets the size to a small phone screen.

beginner

What should you check at each breakpoint during testing?

Check that all buttons, text, images, and menus are visible and usable. Also, check that no content is cut off or overlapping.

What does cy.viewport(1024, 768) do in Cypress?

A Waits for 1024 milliseconds

B Clicks a button with id 1024

C Sets the browser size to 1024 pixels wide and 768 pixels tall

D Opens a new tab with URL 768

cy.viewport(width, height) sets the browser window size to test responsive layouts.

Why is responsive breakpoint testing important?

A To speed up the website loading time

B To check if the website works well on different screen sizes

C To test backend server responses

D To check spelling mistakes

Responsive breakpoint testing ensures the site looks and works well on phones, tablets, and desktops.

Which of these is NOT a common breakpoint size?

A 5000px (super large screen)

B 768px (tablet)

C 1440px (large desktop)

D 320px (small phone)

5000px is not a typical breakpoint size used in responsive design.

In Cypress, how do you test multiple breakpoints efficiently?

A Use cy.viewport() with different sizes inside a loop or multiple tests

B Change the CSS manually each time

C Restart the browser for each size

D Use cy.click() to resize the window

Using cy.viewport() with different sizes in tests automates checking multiple breakpoints.

What should you NOT ignore when testing responsive breakpoints?

A Content visibility and layout

B Button functionality

C Text readability

D Page background color

While background color matters, the main focus is on content visibility, layout, and usability.

Explain how you would write a Cypress test to check a website at three different breakpoints.

Think about setting viewport sizes and running assertions for each.

Why is it important to test responsive breakpoints in automated tests rather than only manually?

Consider benefits of automation vs manual testing.

Practice

1. What is the main purpose of using cy.viewport() in Cypress tests?

easy

A. To capture screenshots of the current page

B. To speed up test execution by skipping UI rendering

C. To mock API responses during tests

D. To simulate different screen sizes for responsive testing

Solution

1. Step 1: Understand cy.viewport() role

   cy.viewport() changes the browser size to simulate devices.

2. Step 2: Identify its use in responsive testing

   This helps check if UI adapts correctly on phones, tablets, and desktops.

3. Final Answer:

   To simulate different screen sizes for responsive testing -> Option D

4. Quick Check:

   cy.viewport() = simulate screen sizes [OK]

Hint: Remember: viewport changes screen size for layout checks [OK]

Common Mistakes:

• Confusing viewport with API mocking
• Thinking it speeds up tests by skipping UI
• Assuming it captures screenshots

2. Which of the following is the correct syntax for the iPhone 6 viewport preset in Cypress?

easy

A. cy.viewport('iphone-6')

B. cy.viewport(375, 667)

C. cy.viewport('iPhone6')

D. cy.setViewport('iphone-6')

Solution

1. Step 1: Recall Cypress viewport presets

   Cypress supports device names like 'iphone-6' in cy.viewport().

2. Step 2: Check syntax correctness

   cy.viewport('iphone-6') uses correct method and exact device name string.

3. Final Answer:

   cy.viewport('iphone-6') -> Option A

4. Quick Check:

   Correct device name string in cy.viewport() [OK]

Hint: Use exact device names in quotes with cy.viewport() [OK]

Common Mistakes:

• Using wrong method name like cy.setViewport()
• Incorrect device name casing or spelling
• Passing numbers without quotes for presets

3. What will be the result of this Cypress test snippet?

cy.viewport('ipad-2')
cy.get('.menu').should('be.visible')

medium

A. Test ignores viewport and checks .menu visibility on default size

B. Test passes if .menu is visible on iPad 2 screen size

C. Test throws syntax error due to missing semicolon

D. Test fails because 'ipad-2' is not a valid viewport preset

Solution

1. Step 1: Understand viewport preset 'ipad-2'

   'ipad-2' is a valid Cypress preset simulating iPad 2 screen size.

2. Step 2: Analyze assertion behavior

   The test checks if element with class .menu is visible at that size.

3. Final Answer:

   Test passes if .menu is visible on iPad 2 screen size -> Option B

4. Quick Check:

   Valid preset + visibility check = pass if visible [OK]

Hint: Valid preset means viewport changes; assertion checks visibility [OK]

Common Mistakes:

• Thinking 'ipad-2' is invalid preset
• Assuming missing semicolons cause errors in Cypress
• Believing viewport is ignored without explicit reload

4. Identify the error in this Cypress test for responsive breakpoint:

cy.viewport(1024, 768)
cy.get('#nav').should('be.visible')
cy.viewport('mobile')
cy.get('#nav').should('not.be.visible')

medium

A. Incorrect selector '#nav' should be '.nav'

B. Missing wait between viewport changes causes flaky test

C. Invalid viewport preset 'mobile' causes test failure

D. Assertions are reversed; nav should be visible on mobile

Solution

1. Step 1: Check viewport presets used

   1024x768 is valid, but 'mobile' is not a recognized preset in Cypress.

2. Step 2: Understand impact of invalid preset

   Using 'mobile' causes Cypress to throw an error and fail the test.

3. Final Answer:

   Invalid viewport preset 'mobile' causes test failure -> Option C

4. Quick Check:

   Use only valid viewport presets [OK]

Hint: Use only Cypress documented viewport presets [OK]

Common Mistakes:

• Assuming 'mobile' is a valid preset
• Thinking missing waits cause failure here
• Confusing selector correctness with viewport issues

5. You want to test a web page's header visibility on desktop (1440x900) and mobile (375x667). Which is the best Cypress test approach?

hard

A. Write two separate tests using cy.viewport(1440, 900) and cy.viewport(375, 667) with visibility assertions

B. Write one test with cy.viewport(1440, 900) only, assuming mobile works the same

C. Use cy.viewport('iphone-x') only, ignoring desktop size

D. Test only on default viewport size without changing viewport

Solution

1. Step 1: Understand responsive testing goal

   We want to verify header visibility on both desktop and mobile screen sizes.

2. Step 2: Choose best Cypress approach

   Writing separate tests with explicit viewport sizes ensures coverage of both layouts.

3. Final Answer:

   Write two separate tests using cy.viewport(1440, 900) and cy.viewport(375, 667) with visibility assertions -> Option A

4. Quick Check:

   Separate viewport tests cover all breakpoints [OK]

Hint: Test each breakpoint separately for reliable responsive checks [OK]

Common Mistakes:

• Assuming one viewport size covers all devices
• Ignoring desktop or mobile viewport testing
• Relying on default viewport without changes