Hi Mason,
thanks for posting, you're right that the documentation could be better here.. we'll try to improve on it over the coming days. The general idea is the following:
1) Save Project should be sufficient, soapUI Pro should only save those items that have actually changed. If you are seeing this is not the case can you diff the (incorrectly) saved files to see if there has in fact been something changed "under the hood"? Or are they exactly the same as the previous version
2) The "Save TestCase" is a way to save specific TestCases if you know they have been changed, without saving other changes that may have been done in the project.. thinking of it, it is kind of superfluous.. hmm..
The way you are supposed to work on composite projects in a team is:
1) Set the project to composite, save it and commit the saved folder structure to some SCM
2) Work on the project and save it when changes have been made, soapUI Pro should only save those files that have actually been changed internally, commit these to your SCM
3) If you update from an SCM, use the "Refresh Composite Project" option on the project menu to bring you project in soapUI into sync with the updated files
Does that make ok sense?
regards!
/Ole
eviware.com
