3 ms·

One reason I can think of is that many engineers really don't do testing. They write tests after the fact because they have to. I've worked with a bunch of engi

One reason I can think of is that many engineers really don't do testing. They write tests after the fact because they have to. I've worked with a bunch of engineers who will code for days then write a few tests "proving" the system works. They have low covergage and are usually brittle. This system would be a godsend in the minds of engineers who think / operate that way. I've also had managers who told me I wasn't allowed to write tests firsts as it was slower. Luckily I was able to override / ignore them as I was on loan "take it up with my boss". They're probbably thinking the same as the above engineers. Another way to think of this is most devs hate documentation... if they had an AI that would write great docs from the code they'd love it. And these to these devs docs they don't have to write are great docs :)

tjpnz 3y ago
>I've also had managers who told me I wasn't allowed to write tests firsts as it was slower. Sounds like a great place to work.
antifa 3y ago
> managers who told me I wasn't allowed to write tests firsts as it was slower. You're suppose to write them together, at the same time. What's slower is spending all of your time mousing around the GUI like a caveman and then having missing tests and then trying to debug every future recurring regression forever the rest of the project's lifespan. The only thing that's slower is perhaps trying to do TDD for the first time. After that, you're embarrassed at how much time you wasted wandering in a browser before your API tests were finished.