Term
|
Definition
| human action that produces an incorrect result |
|
|
Term
|
Definition
| Flaw in component or system that can cause the component or system to fail to perform its required function, Ex. An incorrect statement or data definition. If encountered during execution, may cause a failure of the component or system. |
|
|
Term
|
Definition
| Deviation of the component or system from its expected delivery, service or result |
|
|
Term
|
Definition
| The degree to which a component system or process meets specified requirements and/or user/customer needs and expectations |
|
|
Term
|
Definition
| A factor that could result in future negative consequenses; usually expressed as impact and likelihood |
|
|
Term
|
Definition
| The process of finding, analyzing and removing the causes of failures in software |
|
|
Term
|
Definition
| A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other fomally imposed document |
|
|
Term
|
Definition
| An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, informal review, technical review, inspection, and walkthrough |
|
|
Term
|
Definition
| A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement |
|
|
Term
|
Definition
| The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects |
|
|
Term
|
Definition
| A reason or purpose for designing and executing a test |
|
|
Term
| Exhaustive Testing (Complete Testing) |
|
Definition
| A test approach in which the test suite comprises all combinations of input values and preconditions |
|
|
Term
| Confirmation Testing (Re-testing) |
|
Definition
| Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions. [Note: While the Glossary uses re-testing as the preffered term, this preferance is out of step with ordinary usage and with the actual English language definition of 're-testing'.] |
|
|
Term
|
Definition
| The set of generic and specific conditions, agreed upon with the stakeholders, for permitting a process to be officially completed. The purpose is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing |
|
|
Term
|
Definition
| Any event occuring that requires investigation |
|
|
Term
|
Definition
| Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made. It is performed when the solfware or its environment is changed. |
|
|
Term
|
Definition
| All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be ammended only by way of formal amendment procedure, then the test basis is called a frozen test basis. |
|
|
Term
|
Definition
| An item or event of a component or system that could be verified by one or more test cases, e.g. a function, transaction, feature, quality attribute, or structural element |
|
|
Term
|
Definition
| The degree , expressed as a percentage, to which a specified coverage item has been exercised by a test suite |
|
|
Term
|
Definition
| Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test |
|
|
Term
|
Definition
| The process of running a test on the component or system under test, producing actual result(s) |
|
|
Term
|
Definition
| A chronological record of relevant details about the execution of tests |
|
|
Term
|
Definition
| A document describing the scope, approach, resources and schedule of intended test activities. It identifies among other test items, the features to be tested, the testing task, who will do each test, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process. |
|
|
Term
| Test procedure specification (test procedure, test script, manual test script) |
|
Definition
| A document specifying a sequence of actions for the execution of a test |
|
|
Term
|
Definition
| A high level document describing the principles, approach and major objectives of the organization regarding testing |
|
|
Term
|
Definition
| A set of several test cases for a component or system under test, where the post condition of one test is often used as the procondition for the next one |
|
|
Term
|
Definition
| A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria |
|
|
Term
|
Definition
| Artifacts produced during the test process required to plan, design and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing |
|
|
Term
|
Definition
| A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them. |
|
|
Term
|
Definition
| Separation of responsibilities, which encourages the accomplishment of objective testing |
|
|
