Publish performance test results to Latency Lingo as part of your CI/CD pipeline.

I recommend visiting the Latency Lingo documentation to get familiar.

Locate your API key in account settings and add it as a secret to your Github repository. Next, add the Github Action as a step in your workflow.

The input arguments mimic the flags provided to the publish CLI command.

The value of file should reference a file containing your test results. This depends on your test runner and strategy for running tests in CI/CD. Feel free to reach out for any support.

The action evaluates any thresholds for the test scenario referenced. If any of the thresholds are violated, the action will fail the build.

- name: Latency Lingo
  uses: latency-lingo/github-action@v0.0.2
  with:
    api-key: ${{ secrets.LATENCY_LINGO_API_KEY }}
    file: jmeter-results.jtl
    label: github-action-test

- name: Latency Lingo
  uses: latency-lingo/github-action@v0.0.2
  with:
    api-key: ${{ secrets.LATENCY_LINGO_API_KEY }}
    file: gatling-results.log
    label: github-action-gatling-test
    format: gatling

• Latency Lingo
• Github workflow syntax
• Integration on Github Marketplace
• Integration Github repository