Ved International Discussion Board

Software Testing Type - White Box Testing

Go down

Software Testing Type - White Box Testing Empty Software Testing Type - White Box Testing

Post by jp2012 on Fri Aug 02, 2013 5:43 am

White box testing (a.k.a. clear box testing, glass box testing, transparent box testing, translucent box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. It requires programming skills to identify all paths through the software. The tester chooses test case inputs to exercise paths through the code and determines the appropriate outputs. In electrical hardware testing, every node in a circuit may be probed and measured; an example is in-circuit testing (ICT).

Since the tests are based on the actual implementation, if the implementation changes, the tests probably will need to change, too. For example ICT needs updates if component values change, and needs modified/new fixture if the circuit changes. This adds financial resistance to the change process, thus buggy products may stay buggy. Automated optical inspection (AOI) offers similar component level correctness checking without the cost of ICT fixtures, however changes still require test updates.

While white box testing is applicable at the unit, integration and system levels of the software testing process, it is typically applied to the unit. While it normally tests paths within a unit, it can also test paths between units during integration, and between subsystems during a system level test. Though this method of test design can uncover an overwhelming number of test cases, it might not detect unimplemented parts of the specification or missing requirements, but one can be sure that all paths through the test object are executed.

Typical white box test design techniques include:

* Control flow testing
* Data flow testing
* Branch Testing

The following types of white box testing exist:
--API testing (application programming interface) - Testing of the application using Public and Private APIs.
--Code coverage - creating tests to satisfy some criteria of code coverage. For example, the test designer can create tests to cause all statements in the program to be executed at least once.
--Fault injection methods.
--Mutation testing methods.
--Static testing - White box testing includes all static testing.
jp2012
jp2012
Worker
Worker

Posts : 145
Join date : 2013-06-30
Location : Japan

Back to top Go down

Back to top


 
Permissions in this forum:
You cannot reply to topics in this forum