Forum Discussion
I had a quick google and there seems to be lots of people on web talking about problems with ReadyAPI merge conflicts. You mention youre using got for version control, but not what youre using as your code repository (you do mention other projects using bitbucket).
You mention if you expand a testsuite that introduces a change....for this id suggest collapsing the whole project in the tree, before pushing your changes. If everyone collapses the tree before a push, then that might sort that problem. I cant give you the benefit of my current experience, cos....well.....my place is saving projects as single flat .xml files and the version management software is TFVC! (yeah....dont ask.... 😉).
However, ive done a bit of googling and the following is the result:
Make sure everyone has the pretty print option enabled (its stored in the wsdl preferences)....it'll align the content and keep everyones file formatting aligned (also helpful if you do have to do a manual compare)
Next...i found these helpful points too:
1. Never ever save your Project by pressing Ctrl+S, instead of that save a particular test by right click on test --> Composite Actions --> Save TestCase
2. If any new properties added to Test Suite then add them manually by updating relevant Settings. xmlOpen Setting-xml in Notepad Editor and add new property node as shown below. <con:properties><con:property>
<con:name>key</con:name>
<con:value>value</con:value>
</con:property>
</con:properties>
3. Similar approach for Project level properties, add them manually by opening settings.xml in notepad++ editor and then save
4. Addition of new tests should be also added to element.order manually and save
nmrao posted a fix for the issue of dynamic property values changing each run. He create a script that clears out the property values before the push to remote. See here -->> https://community.smartbear.com/t5/ReadyAPI-Questions/Solution-Script-to-Cleanup-of-Custom-property-values-in-the/m-p/198108#M45275
There's another link i found that provides some tips too -->> https://macadamianlabs.medium.com/tactics-to-overcome-version-control-issues-in-readyapi-38f724ca4827
Finally, you might want to see if adding anything to gitignore helps at all.
Ok....thats all i got im afraid!
Cheers,
Rich
- AlbertSoapUI3 years agoContributor
Hi Rich,
Thank you for your extensive answer.
A quick reply:
- We don't use a repository hosting service like Bitbucket yet. I couldn't find information about it being necessary yet. If so, I would like to find more about it.
- I did see the solution posted by nmrao. I do wonder whether is a less code centered way of working around code sharing issues.
- The points you mentioned about saving testsuites and editing property files where what we ended up in a previous project too. It is good to see them confirmed though.
I will not flag the post as solved yet, as I am curious about other ways of working by other teams and I hope for more replies. As I mentioned we don't have git experienced users in our team and I still find it a bit puzzling that a much used solution like ReadyApi does not have a simple, reliable way of sharing tests with a much used versioning tool as Git or otherwise.
Regards, Albert
Related Content
Recent Discussions
- 14 hours agogroovyguy