MTM: Copy Test Suites from plan A to Plan B fails to keep recorded steps - by SMSBVT

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 775824 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/4/2013 10:56:01 AM
Access Restriction Public


Create a collection of Test Suites in Plan A.  Record steps to the Tests in Plan A.  Copy Test Suites to Plan B. Open a CodedUI project and Generate code from Existing Code, results in a response from system stating that steps have not been recorded.

Now it is safe to assume you chose to do it this way so that fresh tests are generated, if so, it would be nice to have a popup on the copy process that asks if user wants the recorded steps to follow.  However, we moved (copied to destination and deleted from source) 4,000+ Test cases and didn't expect to have to record the steps again.  That was a large amount of time spent correcting the situation.
Sign in to post a comment.
Posted by Microsoft on 3/22/2013 at 2:06 AM

thanks for your feedback. Could you please tell us the version of MTM and TFS that you are using. Also could you give more details on how you are doing the test plan copy?

Posted by Microsoft on 3/20/2013 at 9:52 AM
You have to use cloning of suites instead of copying to persist afn recording. Follow "To clone a test suite and its test cases" from
Posted by Microsoft on 1/7/2013 at 1:15 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/4/2013 at 11:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(