Need Recommendation on Test Data Requirements
We are using RequisitePro to manage Business Requirements and Functional Requirements traced to them. Test Cases in RQM will trace to both kinds of requirements imported form ReqPro. The test data management team needs to also manage a set of test data requirements traced to Test Scenarios. We have not yet structured the RQM 2.0 project and the test scenarios are currently in spreadsheets, waiting for the completion of our tool configuration.
My question is whether we should manage two additional requirement types - Test Scenarios and Test Data Requirements in RequisitePro or can we use requirements native to RQM in addition to imported RequisitePro requirements? Also does RQM 2.0 native requirements support requirement types and tracing between them?
My question is whether we should manage two additional requirement types - Test Scenarios and Test Data Requirements in RequisitePro or can we use requirements native to RQM in addition to imported RequisitePro requirements? Also does RQM 2.0 native requirements support requirement types and tracing between them?
One answer
Hi Cindy,
You can manage your additional test requirements directly in RQM in addition to having the ReqPro integration, if you'd like. ReqPro requirements are imported into RQM, rather than being bridged, so there is a RQM requirement created for each ReqPro requirement.
It is theoretically possible to customize the requirement types but this is an advanced operation and might result in problems with the RQM requirement integration. To do so, you would need to use the thick client and customize the process template. If you're not scared off yet, be sure to experiment in a sandbox environment in case problems arise. I do not believe this is a currently supported scenario, but if you create a child type of Requirement such as "Test Data Requirement" I do not see why it wouldn't work, but again, no promises.
Regards,
John
You can manage your additional test requirements directly in RQM in addition to having the ReqPro integration, if you'd like. ReqPro requirements are imported into RQM, rather than being bridged, so there is a RQM requirement created for each ReqPro requirement.
It is theoretically possible to customize the requirement types but this is an advanced operation and might result in problems with the RQM requirement integration. To do so, you would need to use the thick client and customize the process template. If you're not scared off yet, be sure to experiment in a sandbox environment in case problems arise. I do not believe this is a currently supported scenario, but if you create a child type of Requirement such as "Test Data Requirement" I do not see why it wouldn't work, but again, no promises.
Regards,
John
We are using RequisitePro to manage Business Requirements and Functional Requirements traced to them. Test Cases in RQM will trace to both kinds of requirements imported form ReqPro. The test data management team needs to also manage a set of test data requirements traced to Test Scenarios. We have not yet structured the RQM 2.0 project and the test scenarios are currently in spreadsheets, waiting for the completion of our tool configuration.
My question is whether we should manage two additional requirement types - Test Scenarios and Test Data Requirements in RequisitePro or can we use requirements native to RQM in addition to imported RequisitePro requirements? Also does RQM 2.0 native requirements support requirement types and tracing between them?