Negative assertions (not) in Cypress - Test Execution Trace

Test Overview

This test checks that a specific button is not visible on the page. It verifies that the negative assertion using not works correctly in Cypress.

Test Code - Cypress

Cypress

describe('Negative assertion test', () => {
  it('checks that the submit button is not visible', () => {
    cy.visit('https://example.com/login')
    cy.get('#submit-btn').should('not.be.visible')
  })
})

Execution Trace - 4 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test runner initialized, ready to execute test	-	PASS
2	Browser opens and navigates to 'https://example.com/login'	Login page is loaded in the browser	-	PASS
3	Find element with id 'submit-btn' using cy.get('#submit-btn')	Element '#submit-btn' is located in the DOM	-	PASS
4	Check that '#submit-btn' is not visible using .should('not.be.visible')	Element '#submit-btn' is present but hidden or not displayed	Verify '#submit-btn' is not visible on the page	PASS

Failure Scenario

Failing Condition: The '#submit-btn' element is visible on the page when the test expects it to be hidden

Execution Trace Quiz - 3 Questions

What does the test verify about the '#submit-btn' element?

A That the button is not visible on the page

B That the button is visible on the page

C That the button is enabled

D That the button has the correct text

Key Result

Using negative assertions like 'not.be.visible' helps confirm that unwanted elements are hidden, improving test accuracy and user experience validation.