This is a personal summary of a chapter from the book Agile Testing: A Practical Guide For Testers And Agile Teams. I'm sure you'll find it useful too.
I've worked for seven companies since I became a tester five years ago. I identified a few practices that consistently make my teams happier.
This is a summary of an Ask Me Anything session I did at my company. Developers voted what they wanted to know about (E2E) end-to-end tests and I shared my experience.
With Cypress eventually you will have to assert text. They provide at least three methods: have.text, include.text and contain.text. What's the difference?
I had to test a web app on Chrome, Firefox and IE and I already had the tests in Java using Selenium web driver. So I tried BrowserStack... be careful.
I had automated checks in Java+Selenium, ready for cross-browser testing. I should have asked myself: am I Testing the UI or Testing Through the UI (TuTTu)?
We chose Cypress to automate our E2E tests. I've extracted the best bits of our test repository into this cypress template. No need to start from scratch.
Maybe your page under test that behaves differently based on a config. You can use JS inheritance to avoid duplicated code on PageObjects with Cypress.
I use Selenium for most of my automated checks and PageObjects is a must. With Cypress they recommend AppActions. This is a benchmark between both patterns.
This is a collection of simple and recurring scenarios when writing Cypress tests. It covers setup, assertions, actions, selectors, waits and mocks.
