3 ms·
It’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
by otikik 4y ago
It’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!