Share NameMapping, scripts unit working with team

[douglasv]

Hello, I was thinking about how best to reuse NameMapping and script with other projects, so that a change in one project reflects on another project. File jpg is attachment.

So, only map objects at General Projects.
Merge each NameMapping project at NameMapping from General Projects.

Share generic scripts with others projects(I know it's possible, Script > Add > Existing Item).

About control version at Team Foundation Version Control:
If we are working with teams, is this the better way to share same objects in NameMapping and functions already created ? Is better way to reuse ?

I didn't find something like that.

[AlexKaras · Accepted solution]

Hi,

This is probably the best way.

One thing to know and remember: all files that are part of TestComplete project (except script units to certain extent) are not mergeable and must be marked as binaries in source control system.

[douglasv]

Hi @AlexKaras, did you see shareNameMappingScripts.jpg ? 

I am trying avoid large project, its take time to "upload" to TFS, however i'd like
reuse objects already mapped at my NameMapping and all functions already created in other Projects.

[AlexKaras · Accepted solution]

Hi,

> did you see shareNameMappingScripts.jpg ?

Yes, I saw it.

Not sure if I got the question, but nevertheless:

-- Script code from other project(s) can be reused by utilizing the 'Add Existing' functionality;

-- Only one NameMapping/Aliases file can exist in the project, thus you will have to physically merge NameMapping files from other project(s) into the project where you'd like to use 'combined' NameMapping.

[douglasv]

Hi, @AlexKaras it's ok. Now i see a problem to share, the folder Visualizer inside of TestProject1\Script has almost 100 MB, and to share with TestProject2 take a time.

It's possible delete this folder or their images ?

Thank you.

[AlexKaras]

Hi,

> It's possible delete this folder or their images ?

Yes, the folder may be deleted or just ignored and not included into source control system.

As it is said in the https://support.smartbear.com/testcomplete/docs/working-with/integration/scc/files.html :

"[...] keeping Test Visualizer files in the source control is not recommended due to their large overall file size. Doing so can degrade performance of the check out and check in operations on your test project. [...]"

[douglasv]

Hi, @AlexKaras thank you, i already "push" images to TFS, i 'll try delete this folder and upload again.

[douglasv]

I deleted images from Visualizer, so when i try check in, i still can see images files, is this right ?

[AlexKaras]

Hi,

Not sure, I almost never used Visualizer. Try to check the folder on the disk and delete the folder if it exists.

Or add folder to the ignore list in TFS (I hope such possibility exists in TFS).

[anupamchampati]

1. Try to do Delete All Visualizer Frames from Visualizer properties.

2. Manually delete the Visualizer folder

3. Or Add to Ignore List for all Visualizer folders in the Source Control setting.