SDET Unicorns

Cypress Assertions

Cypress Assertions

Table of Content

In this tutorial, we will cover different types of Cypress Assertions such as the default, implicit and explicit assertions and talk about the difference between the should and the expect assertions.

Cypress uses the Chai assertion library as well as the extensions of Sinon & jQuery to provide you with dozens of powerful assertions for free.

Default Assertions

Cypress comes with many default assertions that can be used without having to explicitly define assertions, such as –

  • cy.visit(): every-time you visit a page, Cypress expects the page to return with a 200 status code
  • cy.get(): the get command expects the element to exist in the DOM first before trying to access it

Implicit Assertions

The implicit assertions used the should() or the and() commands when making assertions. This is the preferable way of making assertions in Cypress.

cy.get('h1').should('have.text', 'My Heading')

You can even chain multiple assertions together –

   .should('have.text', 'My Heading')
   .and('have.class', 'highlighted')

Explicit Assertions

You should use the Explicit assertions when you would like to make multiple assertions for the same subject or when you would like to manipulate your subject before making your assertion. For explicit assertions, you will use the expect command.

cy.get("h1.elementor-heading-title").should(($heading) => {
    // manipulate your text here and assert below
    expect($heading.text()).to.eq("Think different. Make different.");
    // add further expect assertions here

Check out the video below to see learn more about Cypress Assertions –

I hope this post helped you out, let me know if you have any questions in the comments below!

Happy testing! 

My Resources

Thrive Suite: The all-in-one WordPress theme I used to create my blog.
Jasper AI: My favorite AI writing tool.
Surfer SEO:  A tool to help you rank your content on the first page of Google.

Write Content Faster


Write blog posts that rank for affiliate terms!

Join our mailing list

Unlock the Secrets to Becoming a SDET Pro in the Industry!

Stay ahead of the curve! Join our mailing list for exclusive insights, tips, and the latest industry updates delivered straight to your inbox

Table of Content

Related Post

equivalence and boundary value

Understanding Equivalence Partitioning and Boundary Value Analysis in Software Testing

Software testing techniques help ensure software quality and reliability, by helping us select test cases intelligently from the collection of test cases, such that all test scenarios are covered.

Boundary Value Analysis and Equivalence Partitioning are two testing techniques that help testers select a subset of test cases that covers all important test scenarios, even under time and budget constraints. By testing all the equivalence classes and boundary values, testers can reduce the risk of releasing software with defects.

Read More »