| Requirements traceability matrix |
A document that demonstrates the relation between requirements and other artifacts |
| Static test |
Tests that are run without executing the code. It consists of manual and automated reviews. |
| Dynamic test |
Tests that are run while the application is running. |
| Functional test |
Tests that check whether the application is working right. |
| Non-functional tests |
Tests that check whether the application is the right product that meets non-functional requirements like performance, usability, and etc. |
| Change-based testing |
Testing to verify the latest changes and/or their effects on the whole system. |
| White-box testing |
Tests which perform with consideration of internal structure of the software. |
| Black-box testing |
Tests which perform with consideration of specifications of the software. |
| Grey-box testing |
Tests which perform with consideration of specifications and internal structure of the software. |
| Regression test |
Testing an application that has been tested before to be sure that recent changes have not broken anything covered by the regression test suite. |
| Re-test (Confirmation Test) |
Testing a part of the application that contains an untested change that has been tested before. |
| Test data |
Data that was created during or before test design activities. It could be used by the test or application during test execution or implementation. |
| Test design |
A process that test objectives are converted into test deliverables like plans, scenarios, data. |
| Test execution |
The process contains running tests and validating actual and expected results. |
| Test implementation |
A process that test scenarios are detailed (with steps and test data) and/or automated. |
| Work product |
Any output in SDLC (analysis document, code, test scenario, etc.) |
| Author |
Work product creator. |
| Bug/Defect |
A mismatch that might cause a failure in production between the requirement and software. |
| Requirement |
Definition of what customer needs. |
| User Story |
Formatted requirements by using everyday or business language to explain what really user needs including non-functional requirements. It also has acceptance criteria. |
| Acceptance Criteria |
The criteria that software must satisfy to be accepted by the user. |
| Test Script |
Automated or manual scripts to use executing a test. |