← Back to context

Comment by arcticbull

4 years ago

I think you're demonstrating exactly the fallacy that I identified.

I know personally I've caught massive issues in my own unit testing of my own code - so I know for a fact it's not a dead loss of time. I'm also not sure why you think it takes 50% of the workforce - that's never been my experience.

The trick is knowing what to test, how much to test it and how long to spend.

I make 600k ARR with software that has 5% test coverage (ie the clever parts to test).

And the one risk I faced was that I should have used React, because recruitment on this product will fail me i the long term.

Tests are only good for some situations.