4 ms·
Typically you test your software to your needs. If there's a bug in a library you use it would show up when testing your code that uses the library.
by ASneakyFox 12y ago
Typically you test your software to your needs. If there's a bug in a library you use it would show up when testing your code that uses the library.
- mkal_tsr 12y ago> If there's a bug in a library you use it would show up when testing your code that uses the library. That's not true at all. You may catch some lib bugs, but not all, even through testing of your own code that leverages the lib. Unless you're implying that you'll pass every possible value to your tests which will then cover 100% of any and all code in the lib.
- jenscow 12y agoYou, the user of the library, don't care about finding any bugs in parts of the library that your application isn't using. Your tests will be testing the parts of code in the library that your application uses, which is the part that matters to you.
- mkal_tsr 12y agoAre you sure you understand how programming and testing works?
- clarry 12y agoYou can still have bugs in parts of code that you use (or would use) given the right inputs. The problem is making your tests so diverse that they test every possible input.
- ASneakyFox 12y agoYou could. But you'd miss those bugs if you write that code yourself any way.