> 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/guides/test-optimization/test-optimization-playbooks.md). # Test Optimization Playbooks Test Optimization playbooks provide the operational blueprints and configurations required to align testing efforts with code risk. Each playbook is designed to ensure that execution time remains strictly proportional to the scope of a change, maximizing coverage while eliminating redundant effort across all testing stages. ### Test Optimization Playbooks


Automated Testing Optimization	Adjust strategy aggressiveness to ensure that automated execution time is strictly proportional to the scope of change, eliminating wasted compute time on unrelated tests.	Gentler Forest.png	Automated Testing Optimization
Manual Testing Optimization	Transition from "blanket" regression to a risk-proportional model that pinpoints necessary human intervention, freeing QA teams to focus on strategic, high-value exploratory tasks.	Nebula.png	Manual Testing Optimization
Test Optimization for Shift Left Testing	Run hyper-focused suites on feature branches using high-aggressiveness configurations to ensure feedback speed is proportional to the small scope of individual developer changes.	Royal Pink.png	Test Optimization for Shift Left Testing

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/guides/test-optimization/test-optimization-playbooks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.