Black Box Testing

September 12, 2015
Jan
Jan

Beyond white box testing, there’s black box testing at the other end of the spectrum.

When testers don’t know anything about how the software has been put together, they are black box testers.

Their lack of knowledge of the internal structure doesn’t mean that black box testers are completely in the dark. These kinds of testers should get a document or a brief that explains what software is supposed to do. In the case of black box functional testing and test cases, the brief should cover what specific functions or usages the testers should try.

Black box testing is more open-ended, since testers don’t know the internal details of the system or what the developers expect users to do. Since they’re coming to the software without any preconceptions, black box testers can discover a completely different set of bugs and issues.

Read More

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.

February 27, 2020
A test IO Bug's Life

You click submit on a new crowdtest and go home. When you wake, detailed bug reports are waiting in your Jira. But how did they get from the tester to you?

Ship Faster, Sleep Better

Get a Demo
twitterfacebooklinkedin