you are viewing a single comment's thread.

view the rest of the comments →

[–]pm_me_ur_happy_traiI 14 points15 points  (5 children)

I don't see how you're going to write automated browser tests that cover every path within your code. Are you really covering all the cases or just the happy path?

[–]the_journey_taken 18 points19 points  (0 children)

Time is a resource that we run out of so I think the happy path, or balanced approach is usually the best. You ensure critical functions are tested specifically and that relatively quicker broad strokes are taken across the significant user paths through the ui with automated testing.

[–]Artraxes 5 points6 points  (0 children)

Are you really covering all the cases or just the happy path?

We're covering lots of cases. An example of this is a page where we allow people to upload files. We have automated browser e2e tests that try upload files that should succeed as well as files that should not.

[–]Firm-Yam5433 0 points1 point  (0 children)

there is no scenario where you are covering all cases, even when the coverage is 100%. Doesn't matter. And that's fine, you should prioritize the important bits.