If a requirement change for an already executed testcase, is there any way to indicate this?
Scenario:
- Link a TC to one or several requirement(s)
- Freeze the requirement
- Execute the TC
- Edit the requirement by creating a new version
- Now the executed test case should not be valid (IMHO) since the req has changed
Is the above scenario expected behaviour or a bug, or do you not agree on the idea that the TC result shuold not be valid anymore?
Not possible to warn if an executed TC has changed req?
Moderators: Amaradana, TurboPT, TL Developers
Re: Not possible to warn if an executed TC has changed req?
System work this way, there is no interaction bewteen chanes to req and test executions results is not a BUG.
IMHO test case results can not be changed because is log.
May be a feture that allow a report showing what test cases (suggested) has to be re-runed due to req change can be added.
Add feature request with FULLY detailed information on Mantis. Dev team will analize in future is this can be or not an standard feature
IMHO test case results can not be changed because is log.
May be a feture that allow a report showing what test cases (suggested) has to be re-runed due to req change can be added.
Add feature request with FULLY detailed information on Mantis. Dev team will analize in future is this can be or not an standard feature
Re: Not possible to warn if an executed TC has changed req?
Thanks for the reply, I agree, test result should not change, a certain result is always valid for the conditions under it was run. Some form of notification in a report or similar, identifying these test cases would be sufficient. I will add a feature request