RQM 6.0.3: If the RQM workflow is not used to lock the artifacts before test execution, what would be the options to bring about test execution without running the risk of test artifacts getting updated?
RQM 6.0.3 using global configurations and configuration management
If the RQM workflow is not used to lock the artifacts before test execution, what would be the options to bring about test execution without running the risk of test artifacts getting updated?
Creating a separate stream just for test execution is one but then how to do you prevent updation of artifacts in that stream? is there a way to lock all artifacts in a stream when it is created?
|
One answer
Create a baseline? Surely you cannot update anything in the baseline.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.