Performance Test Results

TestBeats supports the following performance test result formats:

✅ JMeter (aggregate.csv)

✅ JMeter JTL

The .jtl file should contain headers and all the requests in test plan should be wrapped around transaction controllers.

Syntax

Command Line Mode

• --jmeter (string) - path to the test result file (csv format).

Configuration Mode

{
  "type": "jmeter",
  "files": ["tests/data/jmeter/sample.csv"],
  "thresholds": [
    {
      "metric": "Duration",
      "checks": ["avg<5000"]
    }
  ]
}

• type (string) - name of the test results file format.

  jmeter

• files (string[]) - path to the test result files. (allows * wild card)

• thresholds (object[]) - pass/fail criteria for test metrics.

  • metric (string) - a measure on how a system performs under test conditions.

    Samples, Duration, Errors, Data Sent, Data Received, Latency

  • checks (string[]) - true/false criteria.

    sum, rate, avg, min, med, max, p90, p95, p99

  • scope (string) - scope of the threshold to be applied on.

    OVERALL, TRANSACTION

  • transactions (string[]) - list of transactions to apply the current threshold.

Examples

Configuration Mode

Sample config file for a JMeter result file.

{
  "targets": [
    {
      "name": "teams",
      "inputs": {
        "url": "<incoming-webhook-url>"
      }
    }
  ],
  "results": [
    {
      "type": "jmeter",
      "files": ["path/to/result.jtl"]
    }
  ]
}

Using Thresholds

Sample config file for a JMeter result file using thresholds.

{
  "targets": [
    {
      "name": "teams",
      "inputs": {
        "url": "<incoming-webhook-url>"
      }
    }
  ],
  "results": [
    {
      "type": "jmeter",
      "files": ["path/to/aggregate.csv"],
      "thresholds": [
        {
          "metric": "Samples",
          "checks": ["sum>1"]
        },
        {
          "metric": "Duration",
          "checks": [ "p95<2000", "avg<2500" ],
          "scope": "TRANSACTION",
          "transactions": ["<transaction-name>"]
        }
      ]
    }
  ]
}