Software Testing Glossary

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.

The ability of software to use an appropriate quantity of resource of certain type (e.g., the amount of main memory and the second level memory, the size of temporary files, etc.) during the work under prescribed conditions.

Software testing process aimed at exploring the usage of resources by a software product.

The result of the performed test. The result may contain all kinds of information on the screen, data changes, bug reports, sent messages.