Support

Yes! Testing serverless functions is a pain point. You do not have visibility into the infrastructure and can’t know where a test fails. Using OpenTelemetry in serverless functions exposes telemetry that you can use for both production visibility and trace-based testing.

Yes! Tracetest provides a Kafka test trigger. It works by emitting events with Kafka to test how consumers process these events. This enables testing the behavior of a message queue by directly validating at the values added and removed from the message queue. You don’t need to test states before and after the message queue, instead validate its behavior directly.

Yes! Tracetest, when combined with your existing Cypress or Playwright test, enables you to full test your complete system, front end to the furthest reaches of your backend system. By capturing a trace with every Cypress or Playwright test, you will be able to pinpoint issues across your full stack. In addition, with trace-based testing, you will be able to assert to ensure proper backend behavior, adding both functional and nonfunctional test coverage.

Tracetest provides you the option of using the cloud based version, or, for companies with stringent security demands, we provide an on premise version which you can install in your own cluster. If you are new to Tracetest, we suggest trying the online demo to see how Tracetest works. When ready, either continue with the cloud version of Tracetest by creating your own organization, or get a license key to install Tracetest on your own Kubernetes cluster.

Yes, Tracetest can be used as part of load testing when integrated with k6. The integration allows you to run trace-based tests alongside k6 load tests, enabling deep assertions and analysis of your system's performance under load.

Yes! The easiest way to reach us is through our Slack Community. We offer dedicated support and onboarding for all new users. You can also reach out to us at support@tracetest.io or the Contact Us form in the nav bar.

Yes, Tracetest allows you to set up automated, recurring tests that can be triggered at specific intervals or based on certain conditions. Scheduled tests ensure that your system behaves as expected over time, catch regressions early, and verify that any changes in production do not introduce new issues. These can typically be configured through CI/CD pipelines, cron jobs, or integrated with other automation tools depending on your setup.

Yes, you can use your existing observability solution with Tracetest, as long as it supports OpenTelemetry or can export trace data in a compatible format. Tracetest is designed to integrate with a variety of observability backends that support OpenTelemetry, including popular solutions like Jaeger, Zipkin, and others.

No, you don't have to add custom Tracetest instrumentation to use Tracetest. Tracetest works with existing OpenTelemetry instrumentation in your application. If your application is already instrumented with OTel, Tracetest can use the traces generated by that instrumentation to create and execute tests.