Software Testing Glossary

Document identifying test objects, their configuration, current status and other information provided by the developers to testers and other interested parties at the early stages of software testing.

The ability of the software to function under the given conditions for a specified period of time or for a certain number of operations.

Model showing the growth of the test component or system reliability, caused by the fixing of faults that had caused denials.

Software testing process with the help of which it is possible to analize the reliability of software product.

The ability of software product to be used instead of another software product for the same goals and in the same environment.

It is conditions or capabilities needed by a user to execute specific tasks or achieve certain goals that must be achieved to fulfill the contract, standards, specifications, or other formal documents.

Tool that provides entry of requirements, their attributes (e.g., priority, responsible staff), annotation.

It is the period in the life cycle of software, within which the software requirements are defined and documented.

Testing technique which validates that the requirements are correct, complete, unambiguous, and logically consistent and allows designing a necessary and sufficient set of test cases from those requirements.

Approach to software testing in which test cases are designed on the objectives and test conditions that appear from requirements.