Browse Prior Art Database

Fast Asynchronous Combinatioral Testing (FACT) method for finding concurrency defects in a software product. Disclosure Number: IPCOM000201863D
Publication Date: 2010-Nov-29
Document File: 6 page(s) / 46K

Publishing Venue

The Prior Art Database


Fast Asynchronous Combinatioral Testing (FACT) method for finding concurrency defects in a software product.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 26% of the total text.

Page 01 of 6

Fast Asynchronous Combinatioral Testing (FACT) method for finding concurrency defects in a software product.

Disclosed is a process providing a capability to spawn multiple finite state machines (FSMs) asynchronously, in a random order against a same software system. By running multiple FSMs in parallel, embodiments of the disclosed process create racing conditions for shared resources, which guarantee variation in an execution profile of each FSM. Embodiments of the disclosed


 rocess stress concurrency and serialization mechanisms to an extent where potential malfunctions and deficiencies are more likely to surface.

Concurrency allows parallel tasks to be performed simultaneously by providing methods for synchronization between processes and data accessed in a computer system. Testing of software systems using concurrency and parallelism typically has issues. For example, in many test methods, functionality tested is executed repeatedly in isolation. Such functionality may involve concurrent execution of multiple-threads and/or processes. When there are concurrency and/or serialization problems within the tested functionality, the testing approach leads to difficulty in uncovering the problems. Without changes in an execution profile,

rocessor scheduling an

                                                      /or resource consumption, repeating a test simply does not yield any new timing conditions. As a result serious software defects may not be undetected.

Common test methodologies used in the software industry today include Unit Testing (UT), Functional Verification Testing (FVT), Regression Testing (RT) and System Verification Testing (SVT). Unit Testing (UT) tests the smallest units of a source code comprising a certain


 iece of functionality including error handling. Functional Verification Testing (FVT) validates implemented function against expected outcome and behavior. FVT should include both successful and error outcomes. Regression Testing (RT) is often automated, and validates already implemented functionality has not been regressed or, in any way, affected by subsequent software changes. System Verification Testing (SVT) typically validates all system components including hardware and software are capable of performing according to functional (and, often



 erformance) specifications under both normal and abnormal (read stress, low resource context, etc.) conditions

When multiple functionalities consisting of concurrent tasks are run together behavior may be unpredictable due to timing of execution, which may prevent referencing an outcome to a known result. The execution is real time situation in which the result is non-deterministic. Known test methods typically target a single specified functionality. While the known methods are important to verify when functionality really performs as required the known methods lack a capability for verifying concurrency issues that may arise when many individually tested and working functionality executes in parallel

The disc...