White Box Testing

September 4, 2015

Since it’s the most widespread style of testing in use, even if you don’t know exactly what white box means, you’re probably doing it.

White box testing is when a programmer writes tests for his or her own code.

Unit testing, integration testing, regression testing, and coverage tests all can fall into this category. White box testers have full access to the source code and understand how the software has been created. When you’re a white box tester, you’re familiar with the inner workings of the product. No matter how hard you try to do otherwise, you test the software based on that knowledge, and with the same assumptions made by the code itself.

White box testing isn’t bad or inferior. It serves a specific and useful function: verifying that a part of the system does exactly what the programmer or tester expects it to do. Without this kind of testing, you have no way of knowing that your upload form works. If you change one line of code months later, the whole system might break without you knowing it - unless you've done your white box unit tests.

Know that your app’s features and functions are working: that’s why white box testing methods are beloved and widely adopted.

Read More

April 18, 2019
The Downfall of Manual Testing

Is manual testing being left in the dust?

April 15, 2019
Customer Conversation: Finding Your QA Fit

Looking to learn more about setting internal quality standards and finding impactful bugs? Hear what our veteran customers had to say!

April 12, 2019
How to Convince Your Boss that Thorough Software Testing is Worth the Money

Thorough testing isn't free, but it can definitely be worth the cost.

Ship Faster, Sleep Better

Get a Demo
Follow us on: