Re:Tests that sometimes fail
by pytester on Tuesday May 28, 2019 @06:53AM
(#20028859)
>There are obvious solutions: Mocking everything, removing global state, writing more robust test setup code... But who has time for this?
I find that doing all of this tends to actually save time overall it's just that the up front investment is high and the payoff is realized over a long time.
Most software teams seem to prefer higher ongoing costs if it comes with quick wins to up front investment.
Re:Tests that sometimes fail
by c0vfefe on Tuesday May 28, 2019 @11:25AM
(#20031068)
Those are the age-old arguments against TDD. Every team will have to analyze the value proposition in their context to see if the return is worth the investment.
I find that doing all of this tends to actually save time overall it's just that the up front investment is high and the payoff is realized over a long time.
Most software teams seem to prefer higher ongoing costs if it comes with quick wins to up front investment.