Keeping Up to Date
Requirements change continuously, so the team needs to keep the test documentation up to date in order to avoid false defects caused by checking products against outdated test documentation.
ALM significantly reduces the effort of maintaining documentation by automating change tracking. Maintaining technical documentation is no longer a problem for projects in which requirements change often. The system automatically stores links between project artifacts, for example between requirements and technical documentation.
When a business or system requirement changes, the system marks the test scenarios that cover it as outdated (not current). All that remains is to filter them in the list and proceed to editing.
In processes with upfront design
The system displays the changes that were made to the requirements, and all that remains is to adjust the corresponding sections of the technical documentation.
In lightweight development processes
If the team works with primary requirements, test documentation is kept up to date using the function tree (functions or epics). User stories and test documentation are linked to functions or epics.
After a story has been implemented, ALM automatically marks as outdated the test scenarios linked to the function (or epic) of that story. All that remains is to open the registry of outdated scenarios, make the required changes, and restore coverage.
