In this section:
| Table of Contents | ||
|---|---|---|
|
Introduction
The Literal and Literal XML input mode is a text field for directly specifying a message or request body. This enables you to work with an existing message, such as a sample from developers, a message traced from the server, and so on. Once a message is copied into the field, you can switch to a Form input mode, which will be populated using schema-aware and schema-constrained heuristics.
Text
Use this option if you want to type or copy a message into the UI. Select the appropriate MIME type, then enter the message in the text field below the Text option.
...
All changes must be saved to be implemented during test execution.
Parameterizing with Hierarchical Data from a Data Repository Data Source
| Anchor | ||||
|---|---|---|---|---|
|
You can parameterize complex XML and JSON elements from a Parasoft Data Repository data source column, which may reference zero, one, or multiple hierarchical record values.
Add a Parasoft Repository Data source. See Creating a Repository Data Source.
Use "ParasoftColumn" to specify which Data Repository column should be used to parameterize that level in the hierarchy of the message. See Hierarchical Parameterization with Literal View.
File
If you already have a file that specifies the message, use this option to indicate the location of that file.
- Enable Persist as Relative Path if you want the path to this file to be saved as a path that is relative to the current configuration file. Enabling this option makes it easier to share tools across multiple machines. If this option is not enabled, the path to this file will be saved as an absolute path.
- Enable Resolve Environment Variables if your file is text and has environment variables that you want resolved. Otherwise, leave this option disabled to improve performance. This option must be disabled if file is binary.
Data Source
If you already have a file containing the various messages you want to use:
...