| || |
System Testing a Change due to UAT Defect
We have a test cycle consisting of phases - Unit Test/System Test/User Acceptance Test.
A defect can be raised at any of these phases.
The question is this:
If you raise a defect at UAT that requires a change and re-release, would you necessarily expect a change/addition to the System Test scripts to test (or even to ensure the change is implemented) the change prior to releasing to UAT?
Re: System Testing a Change due to UAT Defect
If an existing test could have detected the defect prior ot UAT, why did it not detect it? Was the test executed or was it not? If the test was correct, and executed and did not detect the defect, then some failure analyses needs to occur.
If a test existed and was not executed, then the test needs to be added to the test suite normally run prior to promotion to UAT.
There are other if-then-else scenarios here. But I think you get the gist of this.