26 September 2008 - 2.5-beta1 |
What is a Composite Project?
Behind the somewhat bewildering terminology lies a very simple concept; Composite Projects are soapUI projects saved to enable Team Collaboration.
Let's explain more in detail. Normally a soapUI Project is saved as one xml file. This has its advantages; you have only one file to consider and that file contains all information about that project. It also has some disadvantages; collaboration and joint team test development is very hard because synchronization is very hard to do.
When working in a Team in a project you often come to the situation where you have one person updating one test and another person a second test. If you only have one project file this is impossible to do simultaneously and hard to do by synching the test manually.
In comes Composite Projects; composite SoapUI projects are saved as a file system so updating, changing or committing parts of projects, like a TestCase, are much easier to do.
Composite SoapUI project is saved in directory with project name. It contains separate directories for each interface, test suite and mock service and file settings.xml where other project settings and data are stored. Each interface directory contains interface settings.xml file and for each operation one xml file named by operation. Test suite directory contains settings.xml and one xml file for each test case named by test case. Mock service directory contains settings.xml and one xml file for each mock operation named by mock operation.
Making SopaIU project composite is easy. In project properties there is property ,Composite Project that can be true or false. Setting it on true will make project be saved in composite form when saved. Projects that have set Project Password can not be composite.
When renaming element( interface, operation, test suite, test case, etc..) corresponding element in composite file system will be renamed if there is no file or directory with new name. Otherwise error message will be prompted. Deleting element means removing it from file system, too. Trough submenu Composite Actions is possible to save or reload element. For test cases is possible to export, save at designated location, or import them in test suite.