06 August 2007 - 1.7.5 | home user-guide eclipse jbossws intellij netbeans maven 1.X/2.X PDF files forums bugs sourceforge

Home
Getting Started
User Guide

- Overview
  - Tabbed Desktop
  - License Management
  - Preferences
  - XPath Selection
  - Script Library
- Workspaces
- Projects
- Interfaces
  - Interface Viewer
- Operations
- Working with Requests
  - Form Editor
  - Outline Editor
  - Message Inspectors
  - Attachments/Inline Files
- Functional Testing
  - Getting Started
  - TestSuites
  - TestCases
    - Test Requests
      - Assertions
      - Editor Wizards
    - Property Transfers
    - Conditional Gotos
    - Groovy Scripts
      - Examples
      - GroovyUtils
    - Properties Step
    - Delay Step
    - Mock Response
    - DataSource
    - DataSource Loop
  - Property Expansion
- Load Testing
  - Getting Started
  - Limit & Strategies
  - Execution
  - Assertions
  - Diagrams
  - JMeter comparison
- Mocking
  - Getting Started
  - Mock Services
  - Mock Operations
  - Mock Responses
- Usage Scenarios
  - Data-Driven Testing
  - Template-Driven Testing
  - Interactive Testing
  - Surveillance Testing
- Tool Integrations
  - Code Generation
  - WSDL Generation
  - WS-I Tools
  - Apache Tcp-Mon
- CommandLine Tools
  - TestCaseRunner
  - LoadTestRunner
  - MockServiceRunner
  - ToolRunner
- Keyboard shortcuts

IDE/Tool Plugins
Search soapUI site
Project Documentation

- About soapUI
- Project Info
- Project Reports

## Properties Step

The Properties Step allows you to define an arbitrary number of properties that can be used from PropertyTransfer and GroovyScript steps. The properties can optionally be read from/written to a properties-file upon execution, for example if you want to specify some properties external (passwords, endpoints, etc) or want to write some results to a file for later reporting..

### Properties Editor

The Property Step Editor is straightforward:

The toolbar at the top contains the following (left to right):

- Add Property : prompts to add a new property
- Remove Property : prompts to remove the selected property
- Load from : optional field containing a file/URL/system-property that contains the source of the properties. The specified file/URL will be read as a standard properties file and contained property values will be assigned to the steps properties. If the field is set to the name of a system property, this property must in turn specify a file or URL that will be subsequently read as described
- Select Properties Source : allows selection of a local file containing the properties to be read. The selected file will read and the contained properties values will be assigned to matching properties in the Properties Step (you will be prompted if unavailable properties are to be created)
- Save to : optional field containing a file/system-property that contains the target name of properties file. The specified file will be created as a standard properties file and contained property values will be written to it. If the field is set to the name of a system property, this property must in turn specify a file that will be subsequently created as described
- Select Properties Target : allows selection of a local file to which the properties should be written

The table displayed under the toolbar displays the currently defined properties and their values, values and names can be changed by standard editing.

### Details Tab

The Properties Step Details Tab (bottom left) contains 2 options for Property Step execution: Create Missing on Load - creates properties from source property files that are not currently defined Save before Load - specifies to save existing properties before loading new ones to/from the specified source and target property files |

### Step Execution

When a Properties Step is executed during a TestCase, the following actions are taken:

- The properties are read or written from a source if specified as described above (depending on "Save before Load" option)
- The properties are written or read to a target if specified as described above (depending on "Save before Load" option)
- The properties are all copied to the current TestRunContexts properties so they are available for Property Expansion

Next: Delay TestStep