Introduction to Test
The Test discipline acts in many respects as a service provider to the other
disciplines. Testing focuses primarily on the evaluation or assessment of
product quality realized through a number of core practices:
- Finding and documenting defects in software quality.
- Generally advising about perceived software quality.
- Proving the validity of the assumptions made in design and requirement specifications
through concrete demonstration.
- Validating the software product functions as designed.
- Validating that the requirements have been implemented appropriately.
Relation to Other Disciplines
The Test discipline is related to other disciplines.
- The Requirements discipline captures requirements for the
software product, and those requirements are one of the primary inputs for
identifying what tests to perform.
- The Analysis & Design discipline determines the appropriate
design for the software product; this is the another important input for identifying
what tests to perform.
- The Implementation discipline produces builds of the software
product that are validated by the Test discipline. Within an iteration multiple
builds will be tested, typically one per test cycle.
- The Configuration & Change Management discipline controls
change within the project team. The test effort verifies that each change
has been completed appropriately.
- The Project Management discipline plans the project, and the necessary
work in each iteration. Described in an Iteration Plan, this artifact is an
important input to defining the correct evaluation mission for the test effort.
Related Book Content
For exercices, Cyber-Readings or further readings about the Test Discipline, refer the the following book Chapter:
Software Engineering Process - with the UPEDU, Chapter VII: The Test Discipline