-As we said at the end of the previous lesson, black-box testing is - -2
-the testing of the software when we look at it as a black box, - -3
-as a closed box, without looking at it inside, without looking at the - -4
-code. And there are several advantages in - -5
-using black-box testing. So let me recap - -6
-those advantages, some of which we already mentioned, and let me also expand - -7
-on that a little bit. The first advantage of when I mentioned is that - -8
-black box focuses on the domain, on the input domain of the software. And - -9
-as such, we can use it to make sure that we are actually covering - -10
-this domain, that we are actually covering the important behaviors of - -11
-the software. A second advantage is that black box testing does not - -12
-need the code. What that means is that you can perform early - -13
-test design. So you can start designing and writing your test cases, - -14
-even before writing your code, so that when the code is - -15
-ready, we can test it right away. And that helps prevent a - -16
-problem that is very typical in real life software development, which is - -17
-getting an idea of the project and having no time to create - -18
-the tests. In this way, we already have the tests, so - -19
-we just have to run them. Another advantage is that black-box testing - -20
-can catch logic defects, because it focuses on the description of what - -21
-the software should do, and therefore on its logic. If we derive - -22
-test cases from such description, then we can catch these kind of - -23
-problems. And finally, black-box testing is - -24
-applicable at all granularity levels, which - -25
-means that we can use black-box testing in unit testing, integration testing, - -26
-system testing, and so on. We can use it at all levels. -- cgit 1.4.1