Process

The measurements described in this paper answer the question of whether Software Testing is "doing the right thing" (effectiveness). Once there is assurance and quantification of correct testing, metrics should be developed that determine whether or not Software Testing "does the thing right" (efficiency).

This article explains the contents of a quality assurance section for a design specification. It includes reasons why this section is needed by design-time, clarifies the difference between quality assurance and software testing, relates the outline to the V Model, and provides a format easily transferable to other project documents, such as project plans and proposals.

When several different test automation vendors provide similar services, it is sometimes difficult to choose the right test automation software. Clinton Sprauve illustrates how to research various vendors, establish your testing needs, and create a solid plan of attack for the test tool selection process.

Many of the testers reading this article use white box testing techniques based upon the structure of the code. Others conduct primarily black box testing based upon some external specification such as the requirements. And of course, some of them do both. In this short article I will focus on the value of requirements based testing.