cancel
Showing results for 
Search instead for 
Did you mean: 

What Visualizer Files should be put under Source Control, if any?

SOLVED
Contributor

What Visualizer Files should be put under Source Control, if any?

TestComplete's Git plug-in can choose all the necessary files that are needed and optional to enter source control; however, it is recommended by SmartBear not to choose this option as it will include all the image files collected and this can slow down the retrieval process from Git to a user's test box. Therefore, I need to individually select what image files will be needed. I know that image files used for "region tests" a will be stored, which is desired, and I know I won't select the .png files; however, should the TestVisualizer files .tcVis and .xml be choosen for source control?

 

    • .tcVis - Index files that store links to image files shown in the Test Visualizer panel.
    • .png - Images that are shown in the Test Visualizer panel.
    • .xml - Files that store information about the objects displayed in the images shown in the Test Visualizer panel.
3 REPLIES
Highlighted
Contributor

Re: What Visualizer Files should be put under Source Control, if any?

Anyone know? Thank you in advance.

Contributor

Re: What Visualizer Files should be put under Source Control, if any?

Good morning. Anyone have feedback? Hopefully, I've worded my issue well enough to be understandable.

Contributor

Re: What Visualizer Files should be put under Source Control, if any?

I suppose i'm just being overly cautious. I'll just refrain from entering .tcVis and xml into source control for now and see what happens. If anyone has experience with this, please feel free to respond. Thank you in advance.

 

Share Your Stories
Read Latest News
Top Kudoed Authors