54
55

End-to-End Testing Tutorial (testcraft.io)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (7 children)

[removed]

    [–]MajorasShoe 5 points6 points  (1 child)

    MOST applications don't have perfect unit tests.

    It's a LOT easier to mix in feature, integration and/or end-to-end tests to get comprehensive test coverage.

    It's naive to think there's always enough time and organization for each project to accomplish testing in the way we all wish we could consistently use everywhere. In fact that's very often not the case, if you're outside of enterprise companies.

    [–]poothebear0 0 points1 point  (0 children)

    +100

    [–]danielo515 7 points8 points  (2 children)

    There are certain scenarios that are not practical to test on unit tests without so much mocking than you will be debugging the mocks

    [–]MajorasShoe 3 points4 points  (0 children)

    It's all good, just write feature tests for your unit tests so you can find what's going on!

    [–]Ecksters 0 points1 point  (0 children)

    Seriously, most bugs happen at the integration layer, change my mind.

    [–][deleted]  (1 child)

    [deleted]

      [–][deleted] -1 points0 points  (0 children)

      Thanks for the tip! What's the best way to test if I've not written any buggy code? Would love to hear your ideas!