Black Box Testing | Software design and embedded system tools.

Software testing part II (White Box and Black Box testing)

August 19th, 2009 admin No comments

White Box testing
Another name of White box testing is Glass-Box testing or Structural Testing.
It is the test in the system.The tester have to specify the test case that will be used
for test the system.They must have an ability in programming and well understand in
software testing theory.Their task it to assign the test case to every line, every
statement or every path of the program being tested. You can compare white box
testing with the measurement of electronics circuit (In measurement of electronics
circuit,you have to measure the electric current and voltage in every node existing
in your circuit).

White box testing can be applied for testing in Unit testing,Integration testing
or System testing but in commonly the tester apply White box testing in Unit testing phase
of software development.

The advantage of White box testing.
1.The process of White box testing can increase te quality of source code and can make
the pieces of source code work more efficiency because it is the testing in the system
(In the function and in every branches of the code)

2.In White box testing we can look for an error by give an input to the system and monitor
the output from the system.Otherwise it also can look for the internal error that existing
in the mentioned system too.

The disadvantage of White box testing.
1.This kind of testing require high skill in software coding to assure the high-quality of
source code.

Black Box testing.
Another name of Black-Box testing is Functional Testing.It is the testing
that disregard internal mechanism of the system (don’t test the internal component
of the system such as source code or function).This testing method is focus on the
output that come out from the system after we sent the input to it (Output that
come out after the system responded to the input data).

In Black-Box Testing, the tester will not look for the code to test, so the code
is considered to be “Black Box” that we can’t see the content inside the box.The
tester know only they must send the input to the “Black Box” and then it will release
the output to the tester.

The tester usually use the requirement specification document (Requirement
Knowledge) to build the test case, so they know what is the outcome that the system
will send after they send the corresponding input to it.

Now I can summarize the black box testing as follow…
– It is the testing that disregard the source code or command
in the program.
– It is testing of function of system base on the requirement documents.
– The tester must assume for output that will come out from the system
after sending the various input pattern to the system (The output must match up with
the input).

Now I can summarize White Box Testing as follow…
-It is the testing that examine the structure or the work-flow of the program .
-The tester must build the specific test case used for testing in each specific condition.
-The test case must contain the case that can be executed normally and abnormally.
-Try to execute every statement in the function at least 1 time.

Software testing part II (White Box and Black Box testing)

In the next article I will write about Test first method (Software testing part III).
You can see more information about Black box and White box testing at these websites below
1.Software Testing Fundamentals
2.Testing and Code Coverage

Reference site: lenovoblogs

Thank you,
Jitkasem Pintaya.