Test observability
Last updated
Last updated
Tests can be a great source of observability. The ability to study the application in a controlled experiment, changing only the code each time - is a huge opportunity to uncover issues and study how the system behaves.
In practical terms, this means that Digma creates a two-way mapping between the test of each asset - database query, endpoint, code location, or consumer. From the test level, you can identify issues and study system analytics under the test environment.
Interestingly, from the scope of each asset, you can see which tests are triggering it, as well as any related insights and traces.
When you run your integration or end-to-end tests in the IDE, Digma will automatically pick up on that to add observability to each test context. Assuming that the Observability Toggle is turned on, Digma will wrap each test in a trace and begin to analyze which assets were called and how they performed.
Follow the instructions for instrumenting your app in CI as documented here.
You should create unique environments for different test types, to avoid data anomalies and maintain consistency in the analytics.
