Forum Discussion
tristaanogreIt appears you are answering a question I've been trying to get SmartBear support to respond to. As my team keeps having merge conflicts with the ".mds.tcLogs" file, I wrote to SmartBear support and asked them if it would be okay for me to include that file in our ".gitignore" file in Bitbucket. Before doing so, however, I wanted them to confirm for me that I wouldn't be wrecking anything or causing others problems when trying to run tests at a later date/time. Just to confirm here, mate, you are saying it's okay to ignore the .mds.tcLogs file, correct?
SeumasMack wrote:
tristaanogreIt appears you are answering a question I've been trying to get SmartBear support to respond to. As my team keeps having merge conflicts with the ".mds.tcLogs" file, I wrote to SmartBear support and asked them if it would be okay for me to include that file in our ".gitignore" file in Bitbucket. Before doing so, however, I wanted them to confirm for me that I wouldn't be wrecking anything or causing others problems when trying to run tests at a later date/time. Just to confirm here, mate, you are saying it's okay to ignore the .mds.tcLogs file, correct?
Yes.
From the help, indicating files that TestComplete, when integrated with source control, are not included and the reasons why.
Note, that the following files are not added to the source code control:
-
.tcCFGExtender - This file holds tester-specific settings for the project suite (such as the workspace layout).
-
.tcLS - This file contains tester-specific settings for the project suite or project (such as local paths to tested applications, local values of project and project suite variables).
-
.bak - Backup copies of script units.
-
.tlb - This is a type library that contains declarations of events used in the project.
-
.tcLogs - This file contains information on the project suite or project logs.
-
Log files.
-
Project item files that are physically located outside of the project suite folder.
To add detail to the .tcLogs files, these actually are a "linking" file for the project indicating which log entries are associated with the MDS file and where to find them. Everytime a new log entry is created, that file is updated. Because you don't need to version control/source control log files (they aren't source, they are output), you can safeily ignore them... and any other files in the list I just provided.
- tristaanogre5 years agoEsteemed Contributor
In fact... as a quick edit to my post... everything that I listed SHOULD be ignored in your .gitignore file. There is no need for any of them to be version controled and you may even cause problems if you do so.
- SeumasMack5 years agoOccasional Contributor
Thanks, mate. My team and I are brand new to TestComplete and it has given all of us so many headaches. Two of my Test Automation Engineers have moved back over to the Manual Test Team because they refuse to work with TestComplete.
In any event, I appreciate you taking the time to respond to my inquiry. I'm going to update our .gitignore file and include all of the items you presented.
Cheers,
Seumas
- tristaanogre5 years agoEsteemed Contributor
It's a shame that the refuse to learn the tool... TestComplete IS a good tool... but as with any tool, if you use it wrong, you can mess stuff up (ever try opening a glass jar with a hammer? Yeah, it gets the jar open, but not in a useful way). So, learning the tool is important and I'm glad you have the perseverance to do so.
Related Content
- 2 years ago
Recent Discussions
- 15 hours ago
- 2 days ago