It can be a good idea to maintain your properties externally to your SoapUI project. This can help make your projects more flexible when switching between target environments, especially when running SoapUI from scripts (see Chapter 5, Automation and Scripting). In this recipe, we will see how to do this using the Properties TestStep.
I have added a sample properties file called test-properties.txt, which contains the following code:
environmentName=Dev Test invoiceEndpoint=http://localhost:9000 userName=test password=password
There is a completed sample project called PropertiesProject in the Chapter 2 samples.
First, we create a new empty project, TestSuite and TestCase. Then, we add a Property TestStep to read the properties from the test-properties.txt file using a project property to store the file's path. Finally, we write a Groovy TestStep to use property expansions to access the loaded property values from the Property...