Unit Testing for Execution Points

Unit Testing for Execution Points
February 17 13:30 2012 Print This Article

Unit testing is generally conducted to test a small software unit. It is normally carried out by the developer who performed the unit.

Unit testing generally pays the main attention to the execution aspects and uses white-box testing, with different coverage criteria as the exit criteria. It generally pays the main attention to the accomplishable points and related control and data components.

Unit Testing for Execution Points

The generally used software testing techniques for unit testing comprise:

Different Traditional Structural Testing Techniques

Among them: control flow testing and data flow testing are usually used with the models built based on analyzing the code through control flow analysis and data dependency analysis.

Input Domain Partitions

It ground on input variables for the unit. Input domain partitions are usually used to conduct input domain partition testing and related boundary testing.

Ad Hoc Testing

Ad hoc testing or informal debugging are usually used to implement the unit in isolation, generally with the help of some debugging tools to relate specific implementation state to the implementation of specific statements.

Entire statement coverage is a general purpose for such type of software testing. For such units where interplay with other units is necessary, a specific testing environment may require to be used to simulate this interplay without involving other units.

Black-box testing could be conducted on the unit as well, while focusing on the input-output relations.

Nevertheless, it is used much less than white-box coverage testing. The reason is the execution knowledge of the developers who conduct testing of their own code.

Related Posts:

  • No Related Posts

About Article Author

view more articles
Nataliia Vasylyna

View More Articles