Cypress Handling Multiple Tabs

Some websites open links in a new browser tab instead of the current one. Cypress handles this scenario differently compared to tools that can freely switch between multiple tabs. This topic explains the recommended approach.

Why Cypress Restricts Multiple Tabs

Cypress runs inside a single browser tab by design, giving it fast and direct access to that page's content. Supporting multiple tabs would break this direct connection and slow down test execution significantly. This design choice trades some flexibility for speed and reliability.

A Simple Way to Picture It

Think of Cypress as a reporter allowed backstage at only one theater at a time. The reporter gets full access to everything happening in that single theater. Asking the reporter to also watch a second theater across town would break that close, detailed access.

Identifying Links That Open New Tabs

Links that open a new tab usually include a target attribute set to _blank.

<a href="/report" target="_blank">View Report</a>

This attribute tells the browser to open the linked page in a separate tab or window.

Removing the Target Attribute for Testing

A common approach removes the target attribute before clicking the link, forcing it to open in the current tab instead.

cy.get('a[target="_blank"]').invoke('removeAttr', 'target').click()

This trick lets Cypress follow the link normally within its single-tab environment.

Multiple Tab Handling Diagram

Link with target="_blank"
      |
      v
removeAttr('target') removes the new-tab behavior
      |
      v
Click follows the link in the current tab
      |
      v
Cypress verifies the resulting page normally

Verifying the Link Address Without Clicking

Sometimes a test only needs to confirm a link points to the correct address, without actually opening it.

cy.get('#report-link').should('have.attr', 'href', '/report')

This approach avoids the new tab problem entirely by checking the link's destination directly.

Testing the Destination Page Separately

Instead of clicking through a new tab, many teams visit the destination page directly in its own test.

cy.visit('/report')
cy.contains('Sales Report').should('be.visible')

This separates the link behavior test from the destination page's content test, keeping each test focused.

Handling Popup Windows

Some websites open a small popup window instead of a full browser tab, often for authentication flows. Cypress can intercept the window.open function to prevent the popup from appearing, then continue testing the main page.

cy.window().then((win) => {
  cy.stub(win, 'open').as('windowOpen')
})
cy.get('#connect-account').click()
cy.get('@windowOpen').should('be.called')

This pattern confirms the popup attempt happened without actually opening a second window.

Testing Applications with Heavy Tab Usage

Applications relying heavily on multiple tabs for core functionality may need a different testing tool alongside Cypress. Some teams combine Cypress for most tests with another tool specifically for multi-tab scenarios.

Best Practices for This Limitation

Design tests around single-tab verification whenever possible, since this matches Cypress's core strength. Test the destination page directly rather than chasing the new-tab click itself. Reserve alternate tools only for features that truly require simultaneous multi-tab interaction.

Key Points

• Cypress operates within a single browser tab by design.
• Removing the target attribute lets a link open in the current tab for testing.
• Checking a link's href attribute avoids the new tab problem entirely.
• Testing destination pages directly keeps tests focused and reliable.
• Popup windows can be stubbed to confirm an attempt without opening a new window.