How to prevent ReadyAPI from randomly changing how it stores empty XML elements?
Why does ReadyAPI change how it stores a blank XML tag from, say <con:properties/> to <con:properties></con:properties> If I make one change and save, I may see many of these differences, which complicates review of the code. I see this in projects where Composite project is false, and in projects where it is true. The representation of blank XML elements is one of many things about how ReadyAPI stores a project that seem to change at random with each new version or sometimes randomly within the same version. I have tried setting the flag "Pretty prints project files", but this is not sufficient to stop this noise. Is there some other flag I can set so that the method for encoding the project doesn't obscure actual logic changes when I look at the differences? Preferably something that gets remembered in the project, rather than depending on a user setting? References: The following are a few postings that seem relevant, but don't clean up the random XML representations. "Version control - Diff is very confusing for ReadyAPI projects?" https://community.smartbear.com/t5/API-Functional-Security-Testing/Version-control-Diff-is-very-confusing-for-ReadyAPI-projects/m-p/209420#M47734 - Answer: Yes, currently, if you change one thing in ReadyAPI, several things in different places of the project might change as well. "How do I minimize merge conflicts in a ReadyApi composite project when working as part of a team?"https://community.smartbear.com/t5/API-Functional-Security-Testing/How-do-I-minimize-merge-conflicts-in-a-ReadyApi-composite/m-p/141151 - No accepted answer - Recommendation to check the flag "Pretty prints project files" "While this allows you to see exactly what has changed when diff-ing versions, it does have the problem that this is an application setting, thus you have to make sure all users set this value manually on their copies of ReadyAPI (If a user does not set this in their copy ReadyAPI it will revert to saving on a single line). Ideally I would like to see this as a project setting."Solved1.7KViews0likes7CommentsGit Check in issues in Test Complete
Hello Everyone! We have an ongoing issue with checking in our code in Git using Source Control from TestComplete. Scenario: User A and User B are both working on the same project, so they are editing the Name Mapping file simultaneously from two different local machines. Now when it comes to check in the code., User A commits her changes and pushes the changes. User B does a pull, gets the new changes and then commits his changes and pushes the code to Git. However, when User A does a pull to get the changes from User B, she finds numerous merge conflicts in the Name Mapping file, as well as some missing tags. User B also sees the corrupted file in his project. I am trying to understand where are we going wrong here and how can we avoid this issue. It forces us to usually revert the changes to the last working Name Mapping file and we lose part of our work in the process. What is the best method to follow to enable smooth source control without merge conflicts? Any help is greatly appreciated! TaggingAchoubeyto get notified of any response .Solved1.6KViews0likes2CommentsIntegrate all the options that Tortoise Git offers directly into TC
Hello, I order to simplify the installation footprint of using TC with a Git repo it would be really appreciated if all of the GIT options were made available via the default GIT plugin without having to download and install Tortoise GIT. Currently it is barely usable and requires knowledge of GIT command line to create or switch to a new branch. Thanks498Views1like0CommentsUse TortiseGit Client Setting
I have noticed the setting in Options, Use TortiseGit client, keeps getting turned off. Anyone else having this problem? If not, I may have missed setting a .gitignore entry. There are multiple users in the branch currently. Could someone double check me on the file I should be ignoring and the entry I should make in .gitignore? Thanks!Solved2.4KViews0likes9CommentsAdd Perforce Integration for TestComplete
It would be great to have source control integration for Perforce users who are using TestComplete. Currently, it seems the only way to have this is to select the "SCC API Providers Plugin" for the "Current source control plugin:" field on the Source Control dialog. However, I heard from Perforce tech support today that they no longer support their P4SCC plugin. They said I could still download it, but it is only 32-bit and they were not going to develop a 64-bit version. Apparently, according to Perforce, Microsoft no longer supports the SCC API. Perforce tech support also told me that they have not tested P4SCC with TestComplete, so they do not know if it would work.1.5KViews2likes1CommentTell TestComplete not to deal with source control
When I was initially setting up TestComplete, I was poking around in the settings and ran across the Source Control settings. As I recall,the initial setting was something to the effect of "not using source control". I decided to see what would happen if I told it that I was using Git, andI am sorry I did. (I don't want to go into the reasons right now.) Anyway, is there a way to cause TestComplete to forget about my source control system and just keep its hands out of source control altogether?Solved1.3KViews1like1Comment