Two terms that software testers use to describe how they approach their software testing are white box testing and black box testing? Figure display the difference between these two approaches.
Figure With black-box testing, the software tester doesn't know the details of how the software works.
In black-box testing, the tester only knows what the software is supposed to do he can’t look in the box to look how it operates. If he gives a certain input, he gets a certain output. He does not understand how or why it happens, just that it does.
Think of the Calculator in Windows. If we write 3.14159 and push the sqrt button, we get 1.772453102341. With black-box testing, it does not matter what revolution the software passes to compute the square root of Pi. It just does it. Being a software tester, you can also check the result on another "registered" calculator and determine if the Windows Calculator is functioning correctly.
In white-box testing (also known as clear-box testing), the software tester has access to program's code and can analyses it for hints to help him with his testing he can look inside the box. Based on what he sees, the tester may notice that certain numbers are more or less likely to fail and can orient his testing based on that info.
There is a hazard to white-box testing. It's very simple to become biased and fail to objectively test the software because you might tailor the tests to match the code's operation.
0 comments:
Post a Comment