Working with SoapUI Projects

{ArticleIndex} In SoapUI your work is organized into projects which are displayed under the root node in the workspace navigator. A project can contain any number of functional tests, load tests and service simulations required for your testing purposes.

Projects can either be open or closed (via their right button menu); it is recommended to close unused projects which will use less memory and increase SoapUI startup speed.

Add a new project to your workspace either by importing an existing one or by creating a new one, both actions are available from the workspace popup or file menu. Creating a new project prompts you as follows:

1/8

Working with SoapUI Projects

Fill in the name and specify an initial WSDL or WADL file to import, set desired settings and select OK; the project gets created as specified.

When exiting SoapUI, you will be prompted to save any new projects that have not yet been saved; previously saved projects will automatically be saved on exit (unless you select the Exit without saving option from the File menu).

Projects are by default saved into one singe xml-file which contains all project artifacts (interfaces, tests, MockServices, scripts, etc.). If the project contains no external file references, its project file can easily be passed around, checked into a version control system, etc. If the project does contain references to external resource, this will need to be included with the project and preferably referred to using the Resource Root functionality described below.

An auto-save feature is available via the global Preferences UI Settings tab:

Specify the autosave interval in minutes, which will then automatically save all open projects as configured.

Importing and Resolving projects

If you already have an existing project file you can easily import it into your workspace by selecting the Import Project option from the workspace popup menu which will prompt you for

2/8

Working with SoapUI Projects

the project file and add it to the workspace. After imported, SoapUI does a check of the project to see that it is consistent and has all necessary external dependencies available (a process called resolving). If errors are found a Resolve dialog is displayed showing you all errors and giving you options to resolve them as required:

In this example two property files specified in separate TestSteps are missing, the action drop-down for each allows you to select the correct file.

When you are content with the selected (or ignored) resolution(s), press the OK button to start working with the project.

Tip: If you manually want to do a checkup on your project, you can manually select the Resolve option from the project popup menu, which will start the above procedure if any errors are found.

3/8

Working with SoapUI Projects

Remote Projects

SoapUI allows you to import projects over the http protocol, which makes it easy to publish projects (tutorials, demonstrations, bug-reports, etc) on a website which can subsequently be imported into anyones workspace. Select the Import Remote Project option from the workspace popup and specify the URL to the project file; SoapUI will load and import the project just as if it were a regular local projects.

Since it is not possible to save the project file back to the URL, any changes will have to be saved to a local copy upon exit.

The Project Window and Overview

The project window is opened by double-clicking the project node in the navigator; it contains a number of tabs with project-scoped settings and data:

4/8

Working with SoapUI Projects

The the can specification be Overview used to tab enrich of shown a project your above project; description, gives some project-level general data properties on allowing the and contained several project event and scripts allows that initiate Load some Script session Called specific after data, the endpoints, project has been loaded. This can be to for example cleanup Save tasks, for example before removing the passwords project is being or test saved, items, etc. you to perform custom Report Script when generating aetc Project Report as described at The other tabs are related to specific functionalities in SoapUI and will be used covered elsewhere: TestSuites shows all functional TestSuites the Project (see http://www.soapui.org/Fu ) SOAP-bases Security Web Configurations Service (see manages project-level WS-Security configurations for curity.html http://www.soapui.org/SOAP-and-WSDL/applying-ws-se ) in Requirements called manages project requirements (see Projects/managing-requirements.html http://www.soapui.org/Working-with) multiple JDBC scenarios Connections (see manages project level connections that can be used inaspects ml http://www.soapui.org/Working-with-Projects/jdbc-connections.ht ) Reporting manages both global and project-level report templates and parameters (see http://www.soapui.org/Reporting/reporting-infrastructure.html )nctional-Testing/structuring-and-running-tests.html of test Events execution manages (see project-level event-handlers that can be used to(see enhance most html http://www.soapui.org/Scripting-Properties/custom-event-handlers. ) properties - of sets Environments SOAP and REST manages services, project-level environments and JDBC database for connections easy switching between different soapui.org/Functional-Testing/environment-handling-in-soapui.html http://www. )

Project resources

5/8

Working with SoapUI Projects

It is quite common to use external files for holding properties, test-data, etc. When specifying these it is often desirable to specify the path relative to some other folder instead of as an absolute path, which is made possible by the Resource Root property in the bottom left list of properties;

For example, specifying the path d:data here would allow you to specify all remaining paths in your project relative to that folder, for example in an Excel DataSource you could specify just testdata.xls which would during execution resolve to d:datatestdata.xls.

Two parameters are available from the configuration drop-down for this property (as shown in the screenshot):

6/8

Working with SoapUI Projects

- ${projectDir} will resolve files relative to the folder containing the project - ${workspaceDir} will resolve files relative to the folder containing the workspace file

So for example specifying ${projectDir}/data would resolve the above mentioned excel file to be in a folder named <path to project>/data/testdata.xls.

Project Encryption
The Project Password option in the project properties allows you to easily encrypt the entire contents of the project file;

(when saving the project, the project icon will contain a small E to indicate it has been encrypted)

7/8

Working with SoapUI Projects

When opening a project that has been saved with a set password, SoapUI will prompt for this to decrypt the project before use.

To remove the encryption just clear the project password and save the project.

Warning! Dont lose your password; there is no way of recovering an encrypted project file if the password has been lost.

8/8