Namemap versioning
Is there any way to manage multiple versions of a namemap file? For example, I have a namemap file that works with the 2.01 version of our software but I want to create a copy of this namemap for the...
Forum Discussion
I think what I would do is create a second TestComplete project for the testing the new version.
For the tests that are the same in both versions, use Add Existing to put them in the second project. This will create a pointer back to the original test, so even if you edit it in the new project, it's the same file.
For the name mapping, make a copy of the original name mapping file and use Add New to put it in the second project. Edit this one to match your changes for the new version.
For tests that will be unique to either version, use Add New in the appropriate project.
I think what I have decided I will do is make a clone the whole project and make a new project for each release. It seems real silly that I have to do this, but I don't see another way.
It works this way because NameMapping is a part of the project, not an outside file.
Marsha - Not sure what you mean. For example, keyword tests are part of the project but I can have multiple keyword tests. In reality, you can have multiple of everything associated with a project except NameMaps.
True, but TC doesn't know that your keyword tests may be different versions of the same test. They have to have unique names within the project so as far as TC knows, they are all different tests.
What I meant above was, if name mapping could be a file outside the project, like Excel data sheets or other databases are, then multiple projects could share multiple name mappings and it wouldn't be an issue. Since the name mapping is part of the project, it has to be unique.
mfoster711 wrote:I have decided I will do is make a clone the whole project and make a new project for each release.
Since a ProjectSuite can hold numerous related TestComplete projects, why not take advantage of the ProjectSuite/Project hiarchy by adding clones of the existing project within the Project Suite for the new versions? While Marsha makes a valid point about NameMapping, the asertion depends on whether or not the NameMapping item was shared between projects by adding it to a project as an existing item from a base/common project. So if I understand the requirement, after you 'clone' the project in your ProjectSuite, you shoulod have an independent NameMapping item and if not, simply delete it and add a new NameMapping object to the cloned project.
mfoster711 wrote:I have decided I will do is make a clone the whole project and make a new project for each release.
mes6073 wrote:Since a ProjectSuite can hold numerous related TestComplete projects, why not take advantage of the ProjectSuite/Project hiarchy by adding clones of the existing project within the Project Suite for the new versions?
I am confused. Sounds like you are just saying the samething I said. Were you trying to suggest something different?
mfoster711 wrote:I am confused. Sounds like you are just saying the samething I said. Were you trying to suggest something different?
Sorry for the confusion as had the impression you were indicating you would create a copy of the entire projectsuite in a new projectsuite.
