Extended data retention in Test Observability

Learn how your organization can leverage data retention policies on Test Observability.

Test Observability allows users to store their test run data for up to two years.

How long does Test Observability retain my test run data?

Test Observability retains data for set durations based on the plan you are on:

• Free Plan: Upto 60 days
• Observability Pro Plan: Up to 1 year
• Observability Enterprise Plan: Up to 2 years

This data includes test run history and the assertion failure logs. However, video logs are retailed only for 30 days and detailed debug logs are retained only for 60 days for all plans.

The following table summarizes how various types of data are retained for the different plans:

What are the benefits of extended data retention with Test Observability?

The advantages of extended data retention with Test observability are as follows:

Tracking test suite stability & performance improvements

With extended data retention, teams can track the progress and improvements in the software over time. By comparing test results from different iterations, they can assess the impact of optimizations, bug fixes, or enhancements made to the test suite. This information helps to measure the effectiveness of the team’s efforts and progress toward goals.

Identifying recurring issues

Retained test run data allows testers to identify recurring issues or defects that may have resurfaced across multiple testing cycles. By analyzing the historical data, you can recognize the patterns of failure, make data-driven decisions, and focus on addressing the root causes of these problems.

Historical analysis

Retaining test run data allows teams to analyze historical trends and patterns over extended periods.

Testing is a recurring activity that occurs daily. You need to monitor how the effects of your testing activities accumulate over time and take proactive steps to minimize negative impact and maximize progress. Organizations that leverage their data can improve the efficiency of their teams and test suites.

Perform Timeline Debugging to identify the source of an issue

When you uncover a defect during testing, extended data retention allows testers to trace the issue back to its root cause or original occurrence, and do faster RCAs. By analyzing the preserved data, teams can investigate the conditions, inputs, and environment that led to the defect, helping them understand the underlying problems and take corrective actions.

Data retention ensures that a bug is never forgotten. You can always go back and understand an RCA that you might’ve done. For example, if a test suddenly becomes flaky again, you can perform Timeline Debugging and inspect the last period of flakiness to understand what caused it and how it was fixed.

Compliance and audit

In some industries or projects with regulatory requirements, test run data retention may be necessary to comply with legal or industry standards. Preserving test run data allows organizations to demonstrate adherence to regulations and provide evidence during audits.

For organizations that like to maintain a standing log of successfully passed builds and tests as sign-offs before deployments, long-term data retention can help with internal tracking and defining improved standards for software quality.