4 ms·
Tests can carry tech debit, just like any code. They certainly are not identified by it. Tests are one of the ways you have to ensure your code is correct. Con
by marcosdumay 4y ago
Tests can carry tech debit, just like any code. They certainly are not identified by it.
Tests are one of the ways you have to ensure your code is correct. Consequently, they are business-oriented code that exist to support your program usage, and subject to its requirements. How much assurance you need is completely defined by those requirements. (But how you achieve that assurance isn't, and tests are only one of the possible tools for that.)
- hbrn 4y agoThey are still debt since they don't directly contribute to product value: you can delete all your tests and your software will keep functioning. It doesn't mean it's a debt worth taking, though IME most companies are either taking way too much or way to little. Not treating tests as debt typically leads to over-testing, and it is way worse than under-testing. Also, what you're talking about (business-oriented requirements) is more akin to higher level tests (integration/e2e), not unit tests.
- jeremyjh 4y agoIf you can simply delete it that’s not debt, it’s just cost. My bank doesn’t let me delete my loan obligation and still live in my house.
- hbrn 4y agoYou can simply burn the bank, no? I've never seen a team where bad tests were simply deleted. They were always "fixed" instead.
- Rexxar 4y agoYou can also delete the source code after compiling it and your software will keep functioning. Does it mean that code don't directly contribute to product value ?