Debugging: The process of finding, analyzing and removing the causes of failures in software.
Defect: An imperfection or deficiency in a work product where it does not meet its requirements or specifications.
Error: A human action that produces an incorrect result.
Failure: An event in which a component or system does not perform a required function within specified limits.
Quality: The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.
Quality assurance: Part of quality management focused on providing confidence that quality requirements will be fulfilled.
Root cause: A source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.
Test analysis: The activity that identifies test conditions by analyzing the test basis.
Test basis: The body of knowledge used as the basis for test analysis and design.
Test case: A set of preconditions, inputs, actions (where applicable), expected results and post conditions, developed based on test conditions.
Test completion: The activity that makes test assets available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholder test condition An aspect of the test basis that is relevant in order to achieve specific test objectives.
Test control: A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned.
Test data: Data created or selected to satisfy the execution preconditions and inputs to execute one or more test cases.
Test design: The activity of deriving and specifying test cases from test conditions.
Test execution: The process of running a test on the component or system under test, producing actual result(s).
Test execution: schedule A schedule for the execution of test suites within a test cycle.
Test implementation: The activity that prepares the testware needed for test execution based on test analysis and design.
Test monitoring: A test management activity that involves checking the status of testing activities, identifying any variances from the planned or expected status, and reporting status to stakeholders.
Test object: The component or system to be tested. test objective A reason or purpose for designing and executing a test.
Test oracle: A source to determine expected results to compare with the actual result of the system under test.
Test planning: The activity of establishing or updating a test plan.
Test procedure: A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post execution.
Test suite: A set of test cases or test procedures to be executed in a specific test cycle.
Testing: The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
Testware: Work products produced during the test process for use in planning, designing, executing, evaluating and reporting on testing.
Traceability: The degree to which a relationship can be established between two or more work products.
Validation: Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.
Verification: Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
