Whitebox Testing – Is it really white ?
The popular myths around Blackbox & Whitebox Testing are by it’s name. It’s black since we can’t see it (don’t have access to the code) & it’s white since you have access to all the code. But then, With in the code there are many black boxes inside and it’s tough to have access to that code base.
- We don’t have access to code of a language API. Most of the applications have been built on top of a API & assume that the API works fine
- Most of the application do integrate some third party tools over it’s API. We don’t have access to that code base.
- We don’t have access to the code of Compiler
- We don’t have access to code of rum time engine that executes our application code
- We don’t have access to the code of Operating System Services on top of which the application runs
The list goes on and there are many black boxes in side our code too. We are just testing the code written for the application and it’s better to call it as Code Based Testing rather than Whitebox Testing
– Happy Testing..
PageRank
Alexa Rank
Backlinks Google
Backlinks Yahoo
Users Registered
FeedBurner
Facebook
Followers
Since the name is already established we can not change the terms but nevertheless its a good description. Try this site for more clarification http://www.softestclub.com .
Thanks
@Alex,
Terminology being used in the Software Testing community is heavy and different people have different perspectives. Blackbox & Whitebox comes into the category where people say that the name is self explanatory but it’s not.