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
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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