Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SVC2020.2

...

  1. Choose Parasoft> Show View> Smart Test Templates to open the Smart Test Templates view (if not already open).
  2. Click the Add Template button and specify a name and location for the .stt file.
  3. (Optional) You can specify a path to create nested folders to organize your .stt file.
     e
  4. Click Next.
  5. Choose the type of Resource Suite to create. You can create an empty suite or initialize the suite based on a service definition.

    If you are using a definition file, see the following sections for additional information:

    Creating Tests from an OpenAPI/a Swagger Definition

    Creating Tests From a RAML Definition

    Creating Tests From a WADL

  6. Click Next if you are creating a suite based on a service definition and specify the location of your definition file. Skip this step to create an empty suite.
     
  7. Click Finish.
  8. Expand the .stt file and double-click the Resource Suite
  9. (Optional) You can disable the Use Default Name option and specify a name for the file.
  10. Specify a pattern in the Match field to identify the endpoints you want the rules in this suite to apply to (see Configuring Smart API Test Generation). The Resolved field renders a preview of the pattern. Nested Resource Suites inherit the Match settings from the parent Resource Suite. You can determine how to structure template files and configure matching patterns accordingly. See Configuring Smart API Test Generation for a common use-case.  
  11. Right-click the Resource Suite and choose Add New> Resource Template.
  12. (Optional) Disable the Use Default Name option and specify a name for the Resource Template in the Name field.
  13. Choose a method from the Method drop-down menu and specify a pattern in the Match field to identify the endpoints you want the rules in the template to apply to (see Configuring Smart API Test Generation). The Resolved field renders a preview of the pattern. Resource Templates inherit the Match settings from the parent Resource Suite. You can disable the Exact Match option if you want to allow SOAtest to generate tests for all subpaths specified in the Match field. The Exact Match option is enabled by default. 

    When SOAtest determines a match in the Resource Template, configurations from all chained tools are applied. You can determine how to structure template files and configure matching patterns accordingly. See Configuring Smart API Test Generation for a common use-case.

    Info
    titleChaining JSON Assertors

    JSON Assertor tools chained to Resource Templates can be configured to use the values from traffic if present. See Configuring Smart API Test Generation for additional information. 

  14. Right-click the Resource Template and choose Add Output...
  15. Choose a tool to include in your generated test and configure the settings. For example, you can chain and configure an HTTP Authentication tool so that all test suites generated with the template automatically authenticate against the application under test (see Configuring Smart API Test Generation for additional information).
  16. Add additional Resource Suites and Resource Templates as necessary. The .stt file is processed in order from first to last. Each Resource Suite is processed according to its hierarchy before the next suite is processed. You can add as many suites and templates and chain as many tools as necessary to train SOAtest. 
  17. Save your changes.

...