Option to copy test cases under Test Suite when TS is opted to copy under same PA

As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The IBM Engineering team has carefully reviewed this idea, and based on our understanding, it does not fit our near-term plans. Although we are closing this request, it will be kept in IBM's ideas repository. We value your feedback and thank you for allowing us to partner with you in developing our products.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Test Management (formerly Rational Quality Manager- RQM)
Component - Unassigned

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Test Management (formerly Rational Quality Manager- RQM)
Component - Other

According to this use case, another approach would be for the tool to support Test Data record selection criteria at the Test Suite level:
See the following existing enhancement request for this approach: https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=42668

Also, i would like to add that test data is present on the test case level and not on the test suite level. This makes it further impossible for the user to pick a few test cases from a test suite and execute them for a specific test data values.

Also, i would like to add that test data is present on the test case level and not on the test suite level. This makes it further impossible for the user to pick a few test cases from a test suite and execute them for a specific test data values.

Hello, How do you recommend a user to proceed if a test suite has 10 test cases and 7 test cases need to be tested with some test data and may be 5 test cases need to be tested for other test data values. The test data resides in different csv files.

I am still not clear on the need to duplicate the test cases themselves in the scenario described. I would strongly recommend not to duplicate test cases when duplicating test suites unless the test cases need to be modified for a particular test suite.

Hi,

Yes, user is certainly aware of TCER and TSER artifact types. But in some scenarios, where a tester has to test complex testing scenarios in different situations and not all the test cases should be tested in each case, this requested functionality will come handy. It can be really complicated to have hundreds of test cases in one suite then have different TSER and TCERs for that test suite , especially when you dont want to execute all the test cases in different scenarios. In that case it is better to duplicate the test suite and create TSER/TCER as per the requirement.

This is certainly a valid enhancement request.
However, we recommend users to avoid duplication of test artifacts unless really necessary in order to lower the cost of maintenance of the test plans.
It would be interesting to understand why users think they need to duplicate all the test cases when duplicating a test suite.
Are they aware of execution records (TCER and TSER) and how they related to base artifacts?