Skip to content

Instantly share code, notes, and snippets.

@infomaven
Last active May 28, 2024 14:12
Show Gist options
  • Select an option

  • Save infomaven/bee4c2d4c02fd26f26b28d433ee5b97f to your computer and use it in GitHub Desktop.

Select an option

Save infomaven/bee4c2d4c02fd26f26b28d433ee5b97f to your computer and use it in GitHub Desktop.
SoapUI OSS Cheat Sheets

Run SoapUI in Multiple Environments

Any one of these methods can be used to feed an external Endpoint to SoapUI.

  • SoapUI GUI Exclusively
  • Command Line Test Runner (functional, load, security)
  • Custom Groovy Script

Once the method is selected, the SoapUI objects will need to be configured to use the supplied Endpoint.

This algorithm applies whether it is done with code or with the SoapUI Gui.

Ensure the following parameters are defined as global or project level Properties

  • These properties can be loaded into SoapUI from a properties file

  • Typical Values

    Endpoint(s)
    Authentication server (if used)
    DB connection variables (if used)
    Any other items unique to your test environment
    

Regardless of whether done in code or in the GUI, the following would need to happen -

  1. Set Endpoint and Custom Properties at the highest level that makes sense. (for most projects this will be global or project level)
  2. Configure the Interface to point to a Property Expansion that points to the custom property ex. ${#Project#Endpoint}
  3. Configure all TestStep Requests to use the Property Expansion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment