Browse Prior Art Database

FIT? Focused Iterative Testing Disclosure Number: IPCOM000126438D
Original Publication Date: 2005-Jul-18
Included in the Prior Art Database: 2005-Jul-18
Document File: 5 page(s) / 46K

Publishing Venue



Focused Iterative Testing (FIT) -- A methodology designed to find timing related defects within software.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 34% of the total text.

Page 1 of 5

FIT- Focused Iterative Testing

FIT -- Focused Iterative Testing


A new testing methodology is disclosed that has proved to be very effective in the software testing domain. This new testing method is called "FIT" which stands for Focused Iterative Testing. Focused Iterative Testing means testing iteratively against a focus area of a software product. A focus area usually refers to a group of specific features in the software product. When the FIT results meet a certain criteria based on quality, FIT then combines each focus area as building blocks to larger execution scenarios. These larger scenarios are then tested iteratively. This kind of combination and testing is recursively applied to the entire software product until the QA output is satisfactory. FIT is appropriate for any software testing.

    FIT differentiates itself from other software testing methodology by focusing testing area based on known problematic areas, which can be found by performing analysis of the problems that customers hit in the field together with the problems that are found in house during normal testing processes. And FIT provides a method to stress test these specific areas to expose timing/race conditions.

Advantages of FIT:

The advantages of FIT include:

- Increases the probability of finding timing related problems, and hence reduces the number of defects which would otherwise be exposed to the customers.

- Increases the probability of reproducing timing related problems, thus developers would be able to debug and fix the problems found by FIT easily.

- Allows management to use an objective metric to decide when the quality is good enough to ship the product. For example, when the testers can run FIT for a large number of iterations before hitting a problem, this indicates that the quality of the focus area is good and it is ready to ship to the customers. When the testers can only run FIT for a few iterations before hitting a new problem, this indicates the quality of the focus area is weak and it is not ready to ship to the customers. The number of successful iterations that FIT can run without hitting problems gives management the Mean Time To Failure metric (MTTF) which can help management to decide whether the product is good enough to ship or not.

- Allows testers to find out how frequently a problem occurs, and hence enables a developer to prioritize which defects are more important to fix in his defect list.

- Allows new testers to find complicated defects, and hence improves the productivity of new testers.

- Requires less human interaction as the FIT program should be programmed in a way


Page 2 of 5

that does not require any human interaction while the FIT program is being run.

Differences between FIT and Extreme Programming:

The idea of Focused Iterative Testing (FIT) presented here is not the same as the concept of Iteration in Extreme Programming (XP).

    In Extreme Programming one is referring to the entire development and test ...