Source: thenewstack.io
Trace-Based Testing for a Distributed World
Testing has not changed significantly in the last decade in spite of radical shifts in the underlying system architectures that modern development teams use. Distributed architecture has introduced more complexity into both system testing and integration testing.
For that reason, trace-based testing relies on not just data from the response for assertions, but also on data from a tool built for modern architectures — distributed tracing.
Unlike https://tracetest.io/blog/integration-tests-pros-and-cons-of-doubles-vs-trace-based-testing, the test specifications in a trace-based test occur against what is actually recorded as occurring against your system as shown by the distributed traces.
Most trace-based testing solutions allow you to visually build your tests while viewing the response and trace from a triggering transaction.
For that reason, trace-based testing relies on not just data from the response for assertions, but also on data from a tool built for modern architectures — distributed tracing.
Unlike https://tracetest.io/blog/integration-tests-pros-and-cons-of-doubles-vs-trace-based-testing, the test specifications in a trace-based test occur against what is actually recorded as occurring against your system as shown by the distributed traces.
Most trace-based testing solutions allow you to visually build your tests while viewing the response and trace from a triggering transaction.
Related Articles
Community Partners
DevOps Careers