If a load test scenario creates some records in the application, there may be a need to extract the IDs of the new records created during the test or some other dynamic information.

StresStimulus can save values of extractors, data generators, and datasets collected during the test execution to an output file.

Setup test output

Under the Advanced options, the node selects the Test Output Format String property and click the ... button to bring up the Test Output Format String Builder dialog.

Test output options

  1. First, select variables to add to the test output
    1. Select from a list of available data generators and datasets (a)

      Note:

      If the test output includes datasets, then the value will be the concatenation of every cell of the selected row separated by '|'

    2. To see the list of available extractors, select the test case (b) where the extractor is defined
    3. Click the add button (c) to add a variable to the test output list 
  2. To edit the output variable list, use the remove, move-up, and move-down buttons (d)
  3. Optionally, only add values of successful iterations by selecting Exclude failed iterations radio (e)
  4.  Each variable will be a column in the output .csv file. Additionally, the following columns can be added to the output file (f)
    1. Test case name
    2. VU number
    3. Iteration number
    4. Iterations status: can have a value "pass" or "fail"
  5. Finally, set the output file (.csv) options (g). There are two storage options for the location of the file:
    1. Create a new file in the specified folder. Specify an output folder in the Output File/Folder text box. A new output file will be created in the folder after every test run. The file name will have the format: {Date_Time}_Output.csv

    2. Append to the specified file. Specify an output file path in the Output File/Folder text box. On every test run, output data will be appended to the file. Alternatively, tick the Clear file content before every test run checkbox to clear the file before each test run.

      Relative path

      Starting from v5.7 the output file or folder can be a relative path to the main configuration file

  • No labels