Testing and Validation Flashcards
What is the traceability requirements pyramid?
The traceability requirement pyramid is a concept that represents the hierarchy of traceability in software development projects. It illustrates how different levels of requirements traceability contribute to ensuring consistency, completeness, and alignment throughout the software development lifecycle.
What are the components of a traceability requirements pyramid?
needs
features
use cases/support
scenarios
test cases
What are the types of testing and their levels?
The following are ordered from the lowest level with unit testing, to the highest level, with acceptance testing.
Unit testing is done by programmers, and it is very low level.
Unit testing can be split into white-box testing, which is done by checking every line of code to ensure it is correct, or black-box testing which is done by running the code and just fixing errors.
Integration testing is done by system analysts, and sometimes also by business analysts.
This involves UI testing, scenario testing, data flow testing or system interference testing.
UI testing involves ensuring that the user interface is working as expected.
Scenario testing involves ensuring that the scenarios work correctly.
Data flow testing involves ensuring that the data flow works correctly, and happens efficiently.
System interface involves ensuring that interfaces between units work as expected.
System testing is generally focused on NFRs, and is done by the business analyst.
This involves requirements, usability, performance and security.
- This is generally non-tech testing.
- Acceptance testing is done by the users, and involves an
alpha or beta system.
- This can be called user acceptance testing.
What is the purpose of a test plan and/or testing?
To produce documentation that describes how the tester will verify that the system works as intended.
