3 ms·
I'd say that is an architecture problem up to a point. A test does not need any framework. Simply a defined output for a defined input, and then check whether t
by fsloth 9y ago
I'd say that is an architecture problem up to a point. A test does not need any framework. Simply a defined output for a defined input, and then check whether the output matches expectations.
- millstone 9y agoIn this sort of scenario, the bugs lie in the expectations themselves. Tests that don’t account for that are dead weight.
- icebraining 9y agoCan you expand on that? Because I don't see how a test can account for the faulty expectations of the person writing it.