Post #1295636
2026-04-15 06:30 UTC
@tdpauw @samir @mrksdck This is a growing antipattern in the field, but one that is easily sold to management.
“No need for those pesky low level unit tests written by developers - you only need outside in testing! Keep the devs coding, and let someone else write the tests! (SDETs)”
“No unit tests? No problem! It does that as well! Get that code coverage up!”
Finally I’ve heard “But it’s BDD!”
Grifters will grift 🤷♂️
Replies (2)
-
@tdpauw@mastodon.social 2026-04-15 06:36
@thirstybear @samir @mrksdck Yes, I see that in almost all organisations. The whole "SDETs" is an antipattern 🙈 😬 There's nothing wrong with Test Engineers writing automated tests, even writing code if all that is part of implementing a solution. There is a problem if we have a role that writes tests afterwards ...
-
@chrisoldwood@mastodon.social 2026-04-15 07:38
@thirstybear @tdpauw @samir @mrksdck I disagree that e2e tests have to be slow. In the days of Oracle / SQL Server, yes, but eg Mongo’s in-memory mode (added >10y ago) means API acceptance tests took ms to run, and under a minute for the entire suite. You could do outside-in and add unit tests for the gaps. The is exactly how the GOOS book talks about working.