End-to-end tests powered by OpenTelemetry. For QA, Dev, & Ops.

Install |  Documentation |  Twitter |  Discord |  Blog

Click on the image or this link to watch the "Tracetest Intro Video" video (7 mins)

Tracetest is a trace-based testing tool that leverages the data contained in your distributed traces to produce easy to create, yet super powerful integration tests. You can verify activity deep inside your system, even events that occur on 'the other side' of an async message queue. Verifying the timing of different steps in your process via an automated test is also a valuable use case.

• Test by executing a REST or gRPC call to trigger the test. Can also import your Postman Collections.
• Add assertions based on return data from trigger call and/or data contained in the spans in your distributed trace.
• Enables white box testing in which internal structure, design and coding of software are tested to verify flow of input-output and to improve design, usability and security.
• Specify which spans to check in assertions via the advanced selector language.
• Define checks against the attributes in these spans, including properties, return status, or timing.
• Tests can be created via graphical UI or via YAML-based test definition file.
• Use the test definition file to enable Gitops flows.
• Tracetest CLI allows importing & exporting tests, running tests, and more.
• Tests are versioned as the definition of the test is altered.
• Supports numerous backend trace datastores, including Jeager and Grafana Tempo. Tell us which others you want!
• Easy install via Helm command.
• Install can include an example microservice that is instrumented with OpenTelemetry to use as an example application under test.

1. Pick an endpoint to test.
2. Run a test, and get the trace.
3. The trace is the blueprint of your system under test. It shows all the steps the system has taken to execute the request.
4. Use this blueprint to define assertions through Tracetest UI.
5. Add assertions on different services, checking return statuses, data, or even execution times of a system.
6. Run the tests.

Once the test is built, it can be run automatically as part of a build process. Every test has a trace attached, allowing you to immediately see what worked, and what did not, reducing the need to reproduce the problem to see the underlying issue.

The install only takes a few minutes, and is done with via a Helm command. After installing, take a look at the Getting Started guides to set up Tracetest and run your first test.

The Tracetest test definition files are written in a simple YAML format. You can write them directly or build them graphically via the UI. Here is an example of a test which:

• executes POST against the pokemon/import endpoint.
• verifies that the HTTP blocks return a 200 status code.
• verifies all database calls execute in less than 200ms.

id: 5dd03dda-fad2-49f0-b9d9-5143b746c1d0
name: DEMO Pokemon - Import - Import a Pokemon
description: "Import a pokemon"

# Configure how tracetest triggers the operation on your application
trigger:
    type: http
    httpRequest:
        method: POST
        url: http://demo-pokemon-api.demo.svc.cluster.local/pokemon/import
        headers:
            - key: Content-Type
              value: application/json
        body: '{"id":52}'

# Setup what will be asserted on the resulting trace
testDefinition:
    selector: span[tracetest.span.type = "http"]
    - assertions:
        - http.status_code = 200
    selector: span[tracetest.span.type = "database"]
    - assertions:
        - tracetest.span.duration < "50ms"

We are in the our early days with the project and need your help. Have an idea to improve it? Please Create an issue here or join our community on Discord.

Follow us on Twitter at @tracetest_io for updates

Give us a star on Github if you're interested in the project!

Is available at https://kubeshop.github.io/tracetest

MIT License