Forum Posts

sherminsathi6
Apr 03, 2022
In General Discussion
We have written hundreds of end-to-end (e2e) cypress tests and continue to write more as new features are released in different web applications and teams. These tests cover the entire stack, verifying that the most common use cases a customer encounters still work after pushing new code changes into our applications. If you want to take a step back and learn more about how to think about e2e testing in general first, feel free to check out this blog post and come back to it when you're ready. This blog post doesn't require you to be an e2e testing expert, But it does help put you in the right mindset as you'll see why we did things a certain way in our testing. If you're looking for a more in-depth tutorial introducing company mailing list you to cypress testing, we recommend checking out the cypress documentation . In this blog post, we assume that you may have seen or written many cypress tests before and are curious to see how others are writing cypress tests for their own applications. After writing many cypress tests, you will start to notice yourself using similar cypress functions, assertions, and patterns to accomplish What you need. We'll show you the most common parts and strategies we've used or done before with cypress to write tests in separate environments like development or staging. We hope this 1,000 foot overview of how we write cypress tests will give you ideas to compare with your own and help you improve your approach to cypress tests. To present: cypress api overview interact with elements asserting oneself on elements manage apis and services make http requests with cy.Request(…) create reusable plugins with cy.Task() mock
0
0
4

sherminsathi6

More actions