Forum Discussion
Aks1982
10 years agoOccasional Contributor
Standalone project is stored in a single xml file. So when multiple people are working, it becomes difficult to maintain.
Composite project creates a directory structure and stores each testcase as a separate xml, also has separate settings file for test suites and projects.
you need to checkin this directory structure to git or other version control system.
But SoapUI sometimes updates the xml files even though the tests have not changed. ( mostly when you run a testcase from SoapUI, property values stored will change. This would result in testcase xmls being updated eventhough the code has not changed. Becomes difficult to figure out which files to check in if you dont track the code changes done. Other option is leave the checkout directory untouched and have a separate working copy).
if you make changes from SoapUI, make sure you save it first before doing 'refresh composite project'.
You need to do 'refresh composite project' only if you have done some changes through backend, and want to see them in soapUI.
Composite project creates a directory structure and stores each testcase as a separate xml, also has separate settings file for test suites and projects.
you need to checkin this directory structure to git or other version control system.
But SoapUI sometimes updates the xml files even though the tests have not changed. ( mostly when you run a testcase from SoapUI, property values stored will change. This would result in testcase xmls being updated eventhough the code has not changed. Becomes difficult to figure out which files to check in if you dont track the code changes done. Other option is leave the checkout directory untouched and have a separate working copy).
if you make changes from SoapUI, make sure you save it first before doing 'refresh composite project'.
You need to do 'refresh composite project' only if you have done some changes through backend, and want to see them in soapUI.
Related Content
- 7 years agoJSoul