You are reviewing the project's traceability matrix after the first cycle of testing. You have discovered that new requirements have been introduced and others have
changed.
What should you do? [2]
A.
Assign the new requirements to a maintenance release, update the test documentation for the changed requirements.
B.
Ask for more time and budget for testing.
C.
Update the "lessons learned" document to avoid future issues similar to this.
The best action that you should take in this situation is to re-assess the test coverage. This is because the traceability matrix is a document that shows the relationship between the requirements and the test cases, and it can be used to measure the test coverage, which is the degree to which the requirements are tested. If new requirements have been introduced and others have changed, the test coverage may be affected, and some test cases may become obsolete or incomplete. Therefore, you should re-assess the test coverage and update the test cases accordingly, to ensure that the testing is consistent with the current requirements and the test objectives. Traceability Matrix - ISTQB not-for-profit association References: Certified Tester Advanced Level Test Manager (CTAL-TM) - ISTQB not-for-profit association, ISTQB Test Manager Certification - ISTQB Exams Worldwide -ISTQB Official Registration, Traceability Matrix - ISTQB not-for-profit association
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit