Create an identical copy of a keyword test
I'm trying to save a keyword test using "save as" so I keep my original test and make an exact duplicate copy. The Save As will rename my existing test. What's the best way (other than copy all and...
Forum Discussion
Actually, Save As doesn't remove your initial. It creates a copy with a new name. If, after you select "Save as" and save, if you right click on your keyword test node and select "Add -> Existing item" you should be able to find your original.
I recreated and the error I'm getting says "An error occurred in the Team Foundation Version Control client. Reason: the item bla bla bla could not be found in your workspace or you do not have permission to access it.
I'll create a new test that isn't connected to Team Foundation (as I didn't see the one copy I made, wasn't on Team Foundation Server) and try again.
Thanks, I've tried this SAVE As in the past and it just renames the current test. This was before adding files to Team Foundation. Either way, I just created a new test that stayed on my machine, didn't go to the Team Foundation Server at all. It was Test2. I did a Save As Test 22. Now it's renamed as Test22 in TestComplete. When I do the Add to Existing item, it brings me to the location of my current tests on my hdd, and I can only see Test22, not the original Test 2. :( bummer. Thanks though for the instructions!
Well, just tried it myself in TC12.20... and a "Save Current As" creates a copy. Double check something... when you created "Test2"... did you make sure you did a "Save All" first in TestComplete to make sure it was saved to the hard drive? Also, make sure that "Test2" is not being saved in a different location.
The reason I ask is that, when I selected "Add existing item", it took me to a different location than the current path for my project so I needed to actually navigate back to my project to find my original test case. It's possible the original exists... just not where you think it might be... I know, kinda a "duh" thing to check, but I've been caught with silly things like this more often than I'd like to admit so.... :)
You're getting the Team Foundation Version Control error because Test Complete is horrible at version control. If you want to keep your test suite in TFS, you basically have to check everything out as soon as you open the project in Test Complete. Otherwise you will continually get errors while working in Test Complete because Test Complete is not smart enough to check files out as needed. If you're fairly new to TC, you won't have a clue what items should be checked out before you perform some operation anyway. So just check everything out first.
I tried explaining this to Smart Bear tech support, but they didn't want to hear it.
ACTUALLY:
1) I have no problems with TestComplete 12.31 automatically checking out items that are in my TFS source control. If something needs to be checked out, I get a prompt "Do you want to do this?" If I say no, the edit is canceled. If I say yes, it checks out what needs to be checked out and I can do my edits.
2) The "Save As" I can attest that it DOES do a "rename" when using TFS Source Control. This is, certainly, a bit annoying but I don't believe it's TestComplete's fault (if you're not using TFS source control, "Save As" makes a copy). I think TFS tries to be "smart" and apply it as a rename instead of as creating a copy. Perhaps it's something that SmartBear might want to look at but, as I said, I think this is TFS trying to be smart and TestComplete just going along with what TFS is doing.
Thanks for the reply Robert.
Not to be snide or snippy, but you just aren't trying hard enough :)
Yes, there are some operations where you're given a choice to check files out, but in others you only get an error saying the file is readonly with no way to recover. In some cases, if you choose to cancel the operation it only cancels the operation on the one specific file, not the overall operation, leaving your project in a sorry state.
I'm also using 12.31.
