4 ms·
> You have to test that your code, when called, returns a list of items. What do you do when the list it wrong? (eg, not transformed/serialized/sanitized/what
by Supermancho 3y ago
> You have to test that your code, when called, returns a list of items.
What do you do when the list it wrong? (eg, not transformed/serialized/sanitized/whatever)
Sometimes, manual tests show it's not the expected/correct data from the first run;
or later someone adds a line of code (adds a period to a random row). The test runs happy, even thought the data is now incorrect/unexpected.
Moving something that can be automated with mocks, to manual processes, is a bad tradeoff.
- troupo 3y ago> What do you do when the list it wrong? (eg, not transformed/serialized/sanitized/whatever) What do you do when that happens with "regular" unit tests that test every single piece of code in isolation? You fix it. > Moving something that can be automated with mocks, to manual processes Who said anything about manual processes?
- Supermancho 3y ago> Who said anything about manual processes? It's either automated or manual.
- troupo 3y agoWhat is? Where in my comment did I say anything about manual process? Please re-read what I wrote.
- Supermancho 3y ago> What do you do when that happens with "regular" unit tests that test every single piece of code in isolation? > You fix it. If you don't find it via an automated means, it's via a manual means. The implicit assumption is that the error is found, regardless of where that happens, in dev, test, prod, or your env de-jour. Good luck with whatever.