Timeline for Black box or white box testing - which do you do first?
Current License: CC BY-SA 2.5
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2014 at 10:54 | comment | added | Matthieu M. | Then we do not practice TDD the same way. TDD for me is about enforcing the specifications of a class/function: the tests are written to check that the class/function behaves as specified, but could care less how the code behaves behind the scenes so long as those specifications are upheld... which is necessary given that the tests are written before the functionality. | |
| May 17, 2014 at 21:31 | comment | added | Doc Brown | -1, TDD is white box testing. In TDD it is essential to know what the code involved in the test does (and what it does not) to write the next test. Black box testing means that someone who has no idea of the code (a tester, someone who does not even needs to know how to code), designs the tests. | |
| Dec 20, 2010 at 12:46 | history | answered | Matthieu M. | CC BY-SA 2.5 |