ArthurM
Occasional Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Solution Script to Cleanup of Custom property values in the project
nmraogreat job, very accurate and concise scirpt. One thing I have done differently is instead of storing properties to be excluded in lists inside the script, I was using a naming convention - if variable name ends with '*', I treat it as dynamic and clean the value, otherwise treat it as static and leave. I think in a big project, where you have dozens of properties on all levels, might be difficult to keep track of all properties, and using naming convention to differ between dynamic and static properties might be easier. Here is my solution. I am not familiar with 'Save script', looks like a new feature in ReadyAPI. Is it a script that runs as you save the project ?5 years agoPlace ReadyAPI QuestionsReadyAPI Questions4.5KViews1like10CommentsRe: Tactics to Overcome Git Version Control Issues in ReadyAPI
TanyaYatskovska I did a lot of research before coming to this, it showed 2 things: 1. several threads for the same topic shows that many other people have faced similar issues 2. answer of Staff member in this thread leaves us with manually resolving conflicts It is not a question of one issue, I think the part of how XML files are being modified when user makes changes on the GUI level needs significant improvement to eliminate or minimize unsolicited changes - like in the case when reordering one test suite or renaming one API triggers modifications in multiple files. As for custom properties, having a flag for each property to mark it to persist or drop the value after execution could solve the issue of getting conflicts on dynamic properties, however saving current value somewhere for investigation purposes. Without these changes it gets impractical to use ReadyAPI with a big team, which could force one to search for alternatives.6 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews2likes1CommentRe: GIT Integration - Prevent merge conflicts - Property values to be ignored
I tried to come up with some tips to mitigate conflicts, please see here: https://community.smartbear.com/t5/SoapUI-Pro/Tactics-to-Overcome-Git-Version-Control-Issues-in-ReadyAPI/m-p/188598#M432946 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.3KViews1like0CommentsRe: How do I minimize merge conflicts in a ReadyApi composite project when working as part of a team?
I tried to come up with some tips to mitigate conflicts, please see here: https://community.smartbear.com/t5/SoapUI-Pro/Tactics-to-Overcome-Git-Version-Control-Issues-in-ReadyAPI/m-p/188598#M432946 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews1like0CommentsRe: Team work on same composite project
I tried to come up with some tips to mitigate conflicts, please see here: https://community.smartbear.com/t5/SoapUI-Pro/Tactics-to-Overcome-Git-Version-Control-Issues-in-ReadyAPI/m-p/188598#M432946 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0CommentsRe: Ready! API and GIT SCM struggles
I tried to come up with some tips to mitigate conflicts, please see here: https://community.smartbear.com/t5/SoapUI-Pro/Tactics-to-Overcome-Git-Version-Control-Issues-in-ReadyAPI/m-p/188598#M432946 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes0CommentsTactics to Overcome Git Version Control Issues in ReadyAPI
In my recent project my team wasusing Git version control to develop ReadyAPI composite project and we were getting many merge conflicts. Researching ReadyAPI forum I found out that many other people had also faced those issues, so I tried to find a custom solution for our problem, which I described in a recent blog post, hopefully might be useful to someone else: https://medium.com/@macadamianlabs/tactics-to-overcome-version-control-issues-in-readyapi-38f724ca4827Solved6 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.5KViews4likes3Comments