An easier approach to get immediate results (and satisfaction) from the front-end testing world.
I'm working on a big UI Testing Best Practices pr...
For further actions, you may consider blocking this person and/or reporting abuse
Great post! Just a question that I am encountering right now that fits the example in your first video, the signup form. What is the best practice here? Do you use a real dB and you clean it up after every test or you mock a registration? Keep it up!
Hi Filippo! Speaking only about the E2E tests... there are two approaches that depend on the back-end architecture: are the back-end+DB created just for the sake of the tests/pipeline? Or are they the "staging" (but "common" and so reused) ones?
Crystal clear, as always! Thanks for your work 😉
Such a nice article! I work with e2e-tests a lot and it helped me and my team several times finding bugs that unit- and integration tests didn't discover.
The more I work with UI-/e2e-tests, the more I use this top-bottom approach.
Thank you so much!! 🙌
I've just joined DEV to tell you that I love your article. Very well written, relevant and interesting. Neither shallow or obscure. Kudos!
Thank you soooo much 🙏♥️
Super, really nice idea to include the videos 👍
Awesome POST. I was asking myself several times, "why do i need this?" And i was delaying the day to start to learn front-end testing approaches until now.
Thank you for the push :)