Wednesday 25 April 2012

Black box testing

Black box testing:
Testing software without any knowledge of the inner workings, structure or language of the module being tested. Black box tests, as most other kinds of tests, must be written from a definitive source document, such as a specification or requirements document.

Black box testing is, we treat the software application as a black box that we cannot see into. I other words, we have no idea of its inner workings, and we test it, based inputs and expected outputs. As an example, consider a simple calculator application. With Back box testing, we have no idea how the calculator was coded, what language was used, what algorithms are used, how data is stored, etc. You just see a calculator that we can test by entering various calculations and checking that the application gives the correct answer. In practice, Black box testging would only occur in some kind of User Acceptance testing, Beta testing, or some other kind of testing where a third party is doing the testing. For any testind done 'in-house', the tester would typically have at least some knowledge of the architecture of the software. In simple, testing without knowledge of the internal workings of the item being tested. Tests are usually functional.

No comments:

Post a Comment