Test Optimization Timeline
Last updated
Last updated
The traditional build list has evolved into a timeline, providing a visual representation of build history, key events, and changes over time. This new approach offers enhanced insights into the factors influencing savings and testing efficiency.
By presenting build data in a timeline format, users can easily identify trends, correlate events with savings, and understand the impact of different actions on overall performance.
The timeline includes cards, each representing a specific event:
Build events Each build is represented by a card containing essential information such as build name, date, time, TIA status, savings percentage, and number of code changes.
System events
New event type representing automatically triggered actions, such as next scheduled full run.
User action events New event type representing manually triggered actions, such as TIA turned on/off, trigger next run as full run, full run policy update.
Easily navigate to related pages (Build Monitor, Coverage Report, Quality Risk Report) directly from the build card.
To provide additional context on the potential savings achieved, the number of code changes (modified methods) between the current and previous builds is displayed. This metric offers insights into the complexity of the build and the potential for test optimization. A higher number of code changes generally correlates with a lower potential for test savings.
A visual indicator highlights builds where the underlying code changes and subsequent test recommendations have been recalculated due to a change in the reference branch. This provides transparency into the data and helps users understand the impact of branch selection on the presented metrics.
Quickly locate specific builds using the new search functionality.
Key build events and potential issues will be prominently displayed on the corresponding build card. These alerts provide crucial context and enable users to quickly identify areas needing attention. Examples of alerts include: scheduled full runs, timeouts, missing test reports, public API usage, incorrect public API usage and full run errors.
By visualizing build history in a timeline format and providing detailed information within each card, the Savings Breakdown empowers you to identify trends, understand the impact of different actions, and optimize your testing strategy.
