Can SoapUI project files be shared?

Is it possible to split the XML file of a SoapUI project into several small files?

I see that the XML file is a point of contention in code versioning and leads to many merge conflicts. It would be more reasonable if the project was divided into several small files, so that the changes were more isolated; but then we can get a joint configuration between them.

Is there a common solution to this problem? I have never used SoapUI (someone on my team uses it), so I'm probably not aware of SoapUI best practices.

+6
soapui
source share
3 answers

Maybe the "composite project" option meets your requirements: http://www.soapui.org/Working-with-Projects/team-testing-support.html

This option is available only in soapUI Pro.

+8
source share

To solve this part of the question:

I see that the XML file is a competing point in version control of the code and leads to large merge conflicts.

This can help get SoapUI to format the project file in a more VCS-friendly way by fairly printing the project file. Try Preferences -> WSDL Settings -> Pretty Print Project Files

See also Formatting a SoapUI Project File

+3
source share

Below is a small powershell script that parses SoapUI project requests for file sharing. This may be helpful.

 $lookupPath = "C:\temp\soapui-project.xml" $ouputFolder = "C:\temp\out" $invalidChars = [io.path]::GetInvalidFileNamechars() [xml] $contents = Get-Content $lookupPath $ns = @{con="http://eviware.com/soapui/config"} $items = Select-Xml -Xml $contents -XPath '//con:request[@mediaType="application/json"]' -Namespace $ns $nodes = $items | Foreach {$_.Node} $requests = $nodes | % { $fileName = ($_.name -replace "[$invalidChars]","-") + ".txt" $_.request | out-file (join-path $ouputFolder $fileName) } 
+2
source share

All Articles