Responsive breakpoint testing in Cypress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the viewport width to 768 pixels.

Cypress

cy.viewport([1], 800);

Drag options to blanks, or click blank then click option'

A1280

B768

C375

D1024

Attempts:

3 left

💡 Hint

Common Mistakes

Using a width value that is too large or too small for tablet testing.

Confusing width and height parameters.

Setting the viewport width to 768 pixels simulates a tablet screen size for responsive testing.

2fill in blank

medium

Complete the code to check if the navigation menu is visible after resizing the viewport.

Cypress

cy.get('nav').should([1], true);

Drag options to blanks, or click blank then click option'

Acontain

Bexist

Cbe.visible

Dhave.length

Attempts:

3 left

💡 Hint

Common Mistakes

Using exist which only checks presence in the DOM, not visibility.

Using contain which checks text content.

The assertion be.visible checks if the navigation menu is visible on the page.

3fill in blank

hard

Fix the error in the code to correctly set the viewport to a mobile size.

Cypress

cy.viewport([1], 667);

Drag options to blanks, or click blank then click option'

A'375px'

Bwidth

Cmobile

D375

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a string with units like '375px' instead of a number.

Using unsupported keywords instead of numeric values.

The viewport width must be a number, so 375 is correct. Strings with units or keywords cause errors.

4fill in blank

hard

Fill both blanks to test if the footer is hidden on small screens.

Cypress

cy.viewport([1], [2]);
cy.get('footer').should('not.be.visible');

Drag options to blanks, or click blank then click option'

A320

B480

C768

D1024

Attempts:

3 left

💡 Hint

Common Mistakes

Using tablet or desktop sizes instead of small mobile dimensions.

Confusing width and height values.

Setting viewport to 320x480 simulates a small mobile screen where the footer is expected to be hidden.

5fill in blank

hard

Fill all three blanks to create a test that resizes viewport and checks header visibility and width.

Cypress

cy.viewport([1], [2]);
cy.get('header').should('be.visible');
cy.get('header').invoke('css', 'width').should('equal', '[3]px');

Drag options to blanks, or click blank then click option'

A1024

B768

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up width and height values.

Using incorrect width value in the CSS assertion.

The viewport is set to 768x1024 (tablet portrait). The header should be visible and have width 768 pixels.

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