Rapid testing is the testing software faster than usual, without compromising on the standards of quality. It is the technique to test as thorough as reasonable within the constraints. This technique looks at testing as a process of heuristic inquiry and logically speaking it should be based on exploratory testing techniques.
Rapid Testing is a powerful technique that can be used to complement conventional structured testing. It is based on exploratory testing techniques and is used when there is too little time available to obtain full test coverage using conventional methodologies. Rapid Testing finds the biggest bugs in the shortest time and provides the highest value for money of any testing methodology.
Although most projects undergo continuous testing, it does not usually produce the information required to deal with the situations where it is necessary to make an instantaneous assessment of the product’s quality at a particular moment. In most cases the testing is scheduled for just prior to launch and conventional testing techniques often cannot be applied to software that is incomplete or subject to constant change. At times like these Rapid Testing can be used.
The structure of rapid testing is built four components:
- People
- Integrated test process
- Static Testing
- Dynamic Testing
Rapid Testing is based on exploratory testing techniques, which means that the tester has a general test plan in mind but is not constrained by it. The plan can be adapted on-the-fly in response to the results obtained for previous tests. The downside is that it is not possible to guarantee total test coverage, but the benefit is that a skilled tester can quickly home in on faults that would have eluded a scripted test. We often refer to exploratory testing as ‘expert testing’ as it requires a high level of technical knowledge and experience to be effective.
