3 ms·
Honestly, it's pretty rare I find a use case for testing period. If I'm writing a library which contains algorithms or something like that it's pretty easy, se
by bamboozled 4y ago
Honestly, it's pretty rare I find a use case for testing period.
If I'm writing a library which contains algorithms or something like that it's pretty easy, seems useful or necessary.
But a lot of the time I'm gluing things together through API calls and it just seems pointless ?
- otikik 4y agoIt’s exactly the other way around for me. Because a test takes one input and checks the output. An algorithm for, say, quick sort, will “test positive” on the same unit test that uses a brute force approach. A performance test might pick some differences up, but at that point that’s not a unit test any more
- bamboozled 4y agoSo basically, you find it important to test already tested code, with...your own tests?
- otikik 4y agoYes, that is precisely what I said, you got it right. Have a good day!