Written by Paul Cowan✏️
Before I start, I want to point out that I am not referring to one particular project or any particular individual. I beli...
For further actions, you may consider blocking this person and/or reporting abuse
who tests the testers? I asked this once when discussing Automated tests - asking how the code was validated? How was the tests tested? - to make sure they're actually fit for purpose.
People forget, that automated tests are application code that needs maintaining. This is an added expense. They need to be used sensibly.
e2e tests are not there to find new bugs but to prevent a dev to introduce a regression. So the finite input values do make sense, to prevent the next commit to break something.
Its not possible to test every corner-case in an UI test, so you rightly mention the test-pyramid. If your higer-level test found a bug, probably you haven't done enough testing on the lower levels.
I made good experience with e2e tests preventing to introduce regressions and even catching bugs in upstream projects, because they did not test enough.
main reason for selenium vs. cypress:
"Many browsers such as Firefox, Safari, and Internet Explorer are not currently supported."
But what you are right with is, how to measure the effectiveness of a test-suite? I don't have an answer to that
Hey Brian, brilliant article as always.
I will deflect a bit, but how does one get to write for @LogRocket?