Post #1295643
2026-04-15 07:46 UTC
@thirstybear @tdpauw @samir @mrksdck
I’ve just finished a gig where there are only unit and component tests, nothing automated involving the outer layers of the onion. All the non-automated testing involves shared infra because nobody took the time to get that going, so there are huge gaps and it takes time to regression test. They were web APIs and there are Azure local emulators for all the internal dependencies.
Replies (1)
-
@chrisoldwood@mastodon.social 2026-04-15 07:54
@thirstybear @tdpauw @samir @mrksdck I think teams have heard “e2e tests are slow and bad” and avoid them up front, instead of facing into them and adapting *if* they turn out to become a drag on delivery. Don’t throw the baby out with the bath water. (Of course the definition of e2e differs depending on who you’re taking to and what environment you’re in, which doesn’t help matters.)