Tracetest for DevOps, SREs, Observability, and Platform Teams
Stop getting paged in the middle of the night: start using OTel proactively in pre-production to ensure bugs don’t reach production
5 Ways Trace-Based Testing Matters to SREs
![](https://cdn.prod.website-files.com/625f135a8e554e44ad158913/664fbbe6f40074595775a523_tracetest_happy-path%20(1).jpg)
Coverage for your most important flows
- Integrate Tracetest with Playwright and Cypress to fully test your ‘happy path,' verifying both the frontend AND backend flows.
- Your trace is a blueprint when building a test, reducing effort from hours to minutes. No mocking required.
- Schedule tests to run periodically and alert the team of failures, providing synthetic tests across the entire stack.
- Can run in CI/CD and Production.
Enable true end-to-end testing with Cypress and Playwright
- Expand Observability value beyond reactive use by SREs in production.
- Have both Devs and QA Automation Engineers realize the value of instrumenting code by creating trace-based tests.
- Root-cause analysis of failed tests is 80% faster when leveraging Observability in pre-production.
- Orgs using Observability-Driven-Development realize the value of Observability across the entire team. Their instrumentation steadily improves.
![](https://cdn.prod.website-files.com/625f135a8e554e44ad158913/664fc100a396d8b66dbed71c_tracetest-interface-end-to-end-testing%20(1).jpg)
![](https://cdn.prod.website-files.com/625f135a8e554e44ad158913/664fc11549d4f93c70c7127c_tracetest-part-performance-testing%20(1).jpg)
Use Tracetest as part of performance testing
- Work with both k6 and Artillery.io to enable load tests to see inside the black box.
- Validate both functionality and performance of critical backend microservices as part of the load test.
- Use one assertion for multiple services with wildcards! Load tests fail if:
- Any microservice returns a failed status.
- Any database query takes longer than the maximum allowed time.
- Time to complete an asynchronous process exceeds the maximum allowed when under load.
Ensure Observability best practices are followed and enforced
- Ensure traces are following the OpenTelemetry semantic conventions.
- Look for common problems with your traces.
- Get alerts if security best practices are not followed in your traces.
- Enforce quality by failing PRs that don’t meet minimum OpenTelemetry standards.
![](https://cdn.prod.website-files.com/625f135a8e554e44ad158913/664fae5d2d81e8b857bf545b_tracetest_interface_traces_05-2024%20(1).jpg)
![](https://cdn.prod.website-files.com/625f135a8e554e44ad158913/664fc1b9e3e3c966d97683ad_tracetest-Improved-tests_1%20(2).png)
Never get a 3 a.m. wake-up call ever again
- Tracetest allows observability to be used proactively, in tests.
- Improved tests in your CI/CD process can prevent regressions in production.
- Fail PRs that do not pass tests, keeping bugs out of production.
- If the system does break, orgs using Observability Driven Development will have marvelous trace data, improving MTTR and getting back to sleep.