White Box Testing

September 4, 2015
Jan
Jan

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 1, 2020
How test IO helps amplify distributed teams

With remote work capability now a necessity, companies must have the tools in place to enable distributed teams to perform at the highest level. test IO is one of those tools.

March 12, 2020
Tester Spotlight - Alex Che

We’re able to do what we do because of our incredible and diverse community of testers. Meet Alex, a Policeman now QA Engineer who gained the real-world QA experience he needed to change careers testing with test IO.

March 10, 2020
A Benefit of Crowdtesting - Time Compression

When budgeting for crowdtesting in the coming years, it's important to know all the value it adds. Here a little more on one of those values, time compression.

Ship Faster, Sleep Better

Get a Demo
twitterfacebooklinkedin