types of software testing - csmates.com

Types of Software Testing

There are many ways to conduct software testing, but the most common methods rely on the common steps:

During the implementation phase, modules are informally tested by the programmer while they are being coded; this is referred to as desk checking. After the programmer is satisfied that the module appears to function correctly, methodical testing of the module is undertaken by a separate testing team.

There are two basic types of methodical testing.
  • Non-Execution-based testing: The module is reviewed by a team.
  • Execution-based testing: The module is run against test cases.

Non-execution Based Testing

The non-execution-based testing relies on a fault-detection strategy. The fault-detecting power of these non-execution-based techniques leads to rapid, thorough, and early fault detection. The additional time required for code reviews is more than repaid by the increased productivity due to fewer faults at the integration phase.

In general, non-execution-based code testing is less expensive than execution-based testing because:
  • Execution-based testing can be extremely time-consuming.
  • Reviews lead to the detection of faults earlier in the lifecycle.
Non-execution-based testing is also known as static testing.

Execution Based Testing

In this type of testing, the modules are run against test cases. Here are two ways of systematically constructing test data to test a module.

Black-box testing: The code itself is ignored; the only information used in designing test cases is the specification document.
White-box testing: The code itself is tested, without regard to the specifications.

Similar Articles

Post a comment