End-to-End Testing and Feedback Loops #133
beatfactor
announced in
Blog
Replies: 1 comment
-
|
[[Pingback]] Curated as a part of #19th Issue of Software Testing Notes newsletter. https://softwaretestingnotes.substack.com/p/issue-19-software-testing-notes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Among all the types of tests which make up the pyramid of software testing, the end-to-end UI tests are considered by far the most difficult to manage, slow to execute, unstable, flaky, and sometimes even downright impractical. Just consider this recent post from the ThoughtWorks blog – the author recalls a response from an engineering team that was asked about the state of their UI testing:
"Well, we have a couple of Selenium tests, but they're pretty brittle. They always seem to be broken, so we rarely run them.
Not only that, but just by looking at what the team behind the Cypress project write on their website, it seems that software testing doesn't enjoy a favourable reputation among software developers:
“Testing sucks. It’s the part that every developer dreads.”
What is it about UI tests that makes them so brittle and ‘dreaded’? The Cypress team is also claiming that frontend testing hasn’t evolved for the past decade, at least not at the same pace of web development.
Read more
Beta Was this translation helpful? Give feedback.
All reactions