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

## soapUI Pro Form Editor

The form editor attempts to dynamically build a user-friendly input form from the underlying XML-Schema definition for the current request message. The following screenshot shows the form created for one of the paypal api calls;

The toolbar contains buttons to Validate and Clear the current form. Clear will recreate an empty underlying request containg only required elements. Validating will show a clickable list of errors below the editor that can be used to move focus to the corresponding field that caused the error:

By default, the editor creates fields for all elements/attributes in the underlying schema for those structures that are available in the underlying message, which can both be usefull for inspection purposes but also annoying for testing purposes. Therefore, the toolbar contains a "View Type" combo which offers the following options:

- All - will display all fields (default)
- Mandatory - will display only mandatory fields
- Data - will display only fields that contain any data. This can come in handy during testing when preparing a request and wanting to hide remainin fields
- Mandatory and Data - will display all fields containing data and those that are mandatory

For example the follwing shows the above request with the "Data" value selected

This setting will be rememebered between editing sessions.

### Schema Support

The Form Editor supports most commons XML-Schema constructs but may have trouble displaying/editing/validating more complex schemas. Therefore, it is advisable to initially double-check the XML generated by the editor in one of the other editors. Since it is our ambition to fully support XML Schema, please let us know if you have schema constructs that are giving you (or the editor) trouble..

The following constructs should currently work fine:

- Standard elements; if maxOccurs is more than 1 a listbox with add/edit/remove buttons will be shown
- Enumerations/Booleans will be displayed as combo-boxes
- Binary fields are linked to the attachment-support, a "Browse.." button will be displayed next to the input field allowing browsing and automatic associated of a file with a binary field
- Attributes are displayed with a @ before the field name
- Standard Sequence/Choice/All complex types - Choice will be displayed with a combo-box in the section header from which the desired choice should be selected.
- Multiple occurrences of an complex element will be displayed as a list with add/remove buttons in the top right. Each entry in the list will be displayed with a list index next to the section name, for example in the last screenshot above, the MassPayItem section can contain 1-250 MassPayItems, currently it contains only one (seen with an index of [0]).
- AbstractTypes will display a drop-down of global derived types from the schema, allowing selection of which derived type to use

A '*' after a field name denotes that it is required. All fields can show a small green question-mark which will show documentation information from the associated type in a tooltip.

Next: Outline Editor