Tips and suggestions for writing better unit tests

Asayer's platform is  dedicated to providing insights and resources for developers and DevOps teams, focusing on web application monitoring, session replay, and error tracking. Through articles, tutorials, and case studies, Asayer offers insights into visualizing user sessions, reproducing bugs, and optimizing user experiences. Developers and QA engineers can learn about monitoring user interactions, detecting UI/UX issues, and improving web application performance and reliability.

asayer

Cypress is a Javascript-based front-end testing tool that runs in the browser and aids QA engineers and developers with test automation. This article will cover some best practices to use when testing applications with Cypress. As much as the practices covered in this article are Cypress oriented, they can still be applied to any testing platform.

Best practices for testing with Cypress

Selecting elements with data-* attributes to provide context

Avoid testing 3rd party servers that you don’t control and use cy.request when you want to do so

<p>A really good article when starting out with testing.</p>


<p>Great article, selecting with data-* was a tip I wish I had started with instead of ID’s and Classes. I’m glad it’s the first tip in this article.</p>
