NameMapping issues with git sourcecontrol
Hi, I am facing issues with namemapping contents with Source Control. e.g My test scripts contain Aliases of the objects captured and after committing and pushing changes, the version of the namemappi...
Forum Discussion
while this may work if your team works in Silo, but its difficult to create separate projects for all team members and may create challenges with merging.
This works when you create different projects (eg: one project per module, which is my scenario) under the same project suite. I am now dividing my existing project into smaller projects based on modules. I will merge the new Name Mapping file to the existing Name Mapping file for each project. In my team, I am able to dedicate resources to work on separate modules . This kind of works for me. Not an ideal solution for sure, but kind of a workaround.