> 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/use-cases-by-persona/developers.md). # Developers Test Optimization empowers developers to: * **Explore Only Relevant Test Failures:** No more wasting time investigating unrelated test failures. Dive straight into issues impacted by your code changes. * **Achieve Faster Feedback Loops:** Stop waiting for the entire test suite. Test optimization delivers rapid feedback on your code, allowing for swift issue identification and resolution. * **Shift Left Testing and Accelerate Time to Market:** Catch issues earlier in the development process by targeting tests directly related to your changes. Run partial test suites and get your code to market faster. *** ### Exploring Only Relevant Test Failures Test optimization saves developers valuable time by **filtering out irrelevant test failures** and highlighting only those **directly linked to their code changes**. This targeted approach eliminates the need to spend time investigating unrelated issues, allowing developers to **focus their energy on resolving problems truly impacted by their work**. This not only improves developer efficiency and reduces frustration but also helps them: * **Identify the root cause of issues quicker:** By focusing on impacted areas, developers can pinpoint the specific lines of code causing the failure and address them efficiently. * **Prioritize bug fixes effectively:** Understanding which failures are directly related to their changes allows developers to prioritize bug fixes based on potential impact and urgency. * **Reduce debugging time:** Eliminating irrelevant noise from test failures significantly reduces the overall debugging time, allowing developers to move on to new features or bug fixes faster. Implementing test optimization empowers developers to work smarter, not harder, and ultimately deliver high-quality code more efficiently. ### Faster Feedback Loop Traditional testing approaches often involve running the entire test suite after code changes, which can lead to significant delays in receiving feedback. Test optimization empowers developers to **break free from this waiting game** by providing **faster feedback loops**. Here's how: * **Focused Test Selection:** By analyzing code changes, the tool identifies only the tests relevant to those changes. This significantly reduces the overall test execution time compared to running the entire suite. * **Early Issue Detection:** With a smaller, focused test suite running, issues are identified **sooner** in the development cycle. This allows developers to address problems early on, when they are typically easier to fix and have less potential impact on other parts of the codebase. * **Improved Development Flow:** By receiving rapid feedback on their code, developers can iterate and adapt quickly. This **smooths out the development process**, allowing them to move on to new features or bug fixes faster. Test optimization empowers developers to **work efficiently and deliver high-quality code** by providing them with **faster feedback and quicker issue resolution**. ### Shift Left Testing Test optimization fosters **faster delivery cycles** by enabling **"shift-left testing"**. This approach involves **introducing testing activities earlier** in the development process, specifically targeting changes made in the code. By using test optimization: * **You focus on relevant tests:** Only tests linked directly to your code changes are executed, **reducing overall testing time**. * **Issues are caught earlier:** By testing changes as they happen, problems are identified **sooner** in the development lifecycle, before they can propagate and become more complex to fix. * **Time to market is accelerated:** Faster test cycles and earlier bug detection lead to **quicker overall development**, allowing you to get your code to market faster. Test optimization empowers developers to be **more proactive and efficient** throughout the development process, ultimately contributing to **faster and higher-quality releases**. --- # 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/guides/test-optimization/use-cases-by-persona/developers.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.