> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/knowledge-base/sealights-for-abap/test-optimization/test-optimization-savings-breakdown.md). # Test Optimization Savings Breakdown Test Optimization Savings Breakdown provides a comprehensive overview of test execution performance and savings for a specific app and test stage. ## Timeline The page includes a timeline with: * Transport events, with a summary of the test savings (or potential savings) out of the total tests reported * System events (e.g. scheduled full test run) * User action events (e.g. TIA turned off/on, full run policy change). ## Test Execution Data & Insights Users can view test execution data and detailed insights into each individual transport, including: * **Test Execution Summary and List:** The total number of tests passed / failed, executed / skipped, along with the skipping reason. And a detailed list of all reported tests. * **Impacted Tests:** Detailed list of code changes and their corresponding tests for each transport. ## Charts & Graphs Users can open an additional view with charts describing the savings (in compute time or in number of tests) per transport, with a clear visualization of the trends over time and the ability to analyze the potential savings before turning on the TIA. *** By combining these elements, the Savings Breakdown empowers users to understand the factors driving test efficiency, pinpoint areas for improvement, and make data-driven decisions to optimize testing processes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sealights.io/knowledgebase/knowledge-base/sealights-for-abap/test-optimization/test-optimization-savings-breakdown.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.