Defining a Database Property Set

Document created by Chris Sommerstad Employee on Jul 20, 2017
Version 1Show Document
  • View in full screen mode

CloudTest provides the ability to create user-defined property sets per database action. A database action property set is created on the response (e.g. the same response that is posted to Result Details per database action. In general, you should create your custom properties prior to beginning.

Users can do extraction by the (default) Substring method to extract a value and store it into a property, or, extraction can be doneuse Glob, Regex, or XPath to do the extraction. Property Sets for database actions are defined in Clip Editor, List view, or from Icon view via the Clip Editor lower panel, Action Editor.

    1. Before defining a property set, create at least one of the custom properties to use. For example, create a Clip Custom Property in the test clip that has the database action.
    2. To configure a property set for a database action, do either of the following:
      • In List view, select and expand the action whose response you’d like to extract into a property.

  • In Icon view, select and double-click the database action to open it in the lower panel.

 

  1. Click the Property Set icon (in List view) or the Property Sets tab and green Plus (+) icon (in Icon view).

The New Property Set form is added to the action.

  1. Give the new property set a name.
  2. In the Retrieved Using field select from among:

 

  • Substring – The following script is expected to succeed
  • Exact Match – Matches exactly
  • RegEx – Matches regular expression
  • Glob – Matches glob expression

 

Depending on the selection made here, the remainder of the form changes accordingly. Refer to the following sections depending on the option selected here.

User-Defined Database Property Sets using Substring

Use the following steps if the default, Substring, was chosen above.

  1. Specify the Leading Text before the string by selecting it and clicking Insert Selected on that row. This will include it in the string search.
  2. Specify the Trailing Text after the string by selecting it to include and clicking Insert Selected on that row. Using Trailing Text will further delimit the sub-string search.
  3. Optionally, specify the value length to search.

  1. Accept the default Multi-Match, all value(s), or select from any of the following values:
    • the first – Use the first value matched
    • the last– Use the last value matched
    • specific index - Pick the nth value, where n is entered. When specific index is selected, an entry field appears for the user to specify the nth value. Indexes start at 1. 0 is not allowed.
    • one at random - Randomly pick one of the matched values to populate the property.
    • all values – The all values field will place all values into a non-array. This option has the functionality formerly found in the pre-SOASTA 50 "all values (array)" field--only the label has been changed. If the match will necessarily be an array, use all values (array) instead
    • all values (array) – This field is new as of SOASTA 50, but uses the old label all values (array). This "new and improved" version of all values (array) will always create an array (whereas prior to SOASTA 50 using the field with this label did NOT always create an array).
  2. Specify the No Match failure action from among:
    • fail the Clip Element
    • return null
  3. If the property to store the extracted value doesn't yet exist. Create it now, before proceeding. the Click Property to set to access the Property Chooser box. If the property to store the extracted value doesn't yet exist, create it here by Manually If you're creating a custom property, you can also do so in advance of creating your property set so that you can select it here.

Attachments

    Outcomes