I love the "Call to Test" feature when writing test steps and this was a big selling point for us. However I recently noticed that if I clone a test cast that uses "Call to Test", that the called tests are also being cloned. This is exactly what I don't want to happen.
I can't imaging that this is the designed behavior. When I reached out to customer service they said this was the intended behavior. I hate this and for us it defeats the purpose of the "Call to Test" feature.
We have a some basic app functionality for performing operations like environmental setup and post-action verifications that need to be executed for many tests, and sometimes these actions change. Instead of writing the discrete steps for dozens or hundreds of Test Cases, we want to use "Call to Test". Then if the action changes we only have to update that Called test.
If the "Call to Test" test is cloned when I clone a Test Case, I now have to edit the cloned Test Case to point to the originally intended Called test, and delete the clone of the Called test. Otherwise I will have unwanted copies of the Called test which defeats the power of having this; creates a maintenance nightmare; and destroys the tractability I'm looking for to track how often the Called test is run and it's results.
I'm sure there are users that like the way this feature works, but I'd like to have an option to not clone the "Call to Test" steps and instead just clone the step to point to the same "Called to Test" test as with the original Test Case.
