> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/test-optimization-1/getting-started.md).

# Getting Started

Test Optimization significantly **slashes testing timelines by 50% to 90%** and **reduces resource expenses by up to 70%**, enhancing both automated and manual testing.

It intelligently cherry-picks essential tests linked to code changes across various test types, employing machine learning for precise coverage without compromising quality.

This functionality is adaptable, seamlessly functioning within pull requests, nightly test runs and extensive test cycles (automated or manual).

### The Three Pillars of Testing Efficiency

{% tabs %}
{% tab title="Shorten Release Cycles" %}
Optimizing your test suite significantly slashes CI/CD compute usage and infrastructure bills. Additionally, by automating the "what to test" decision, you eliminate repetitive manual regression and free your QA team for high-value strategic tasks.
{% endtab %}

{% tab title="Reduce Troubleshooting" %}
By isolating tests to specific code changes, SeaLights makes debugging effortless. When a test fails, you know exactly which change caused it, removing the guesswork and "noise" of massive regression suites so you can fix issues in minutes, not hours.
{% endtab %}

{% tab title="Reduce Costs & Infra" %}
SeaLights slashes operational overhead by pruning redundant test executions. By optimizing your test suite, you reduce CI/CD compute usage and environment wear-and-tear, significantly lowering infrastructure bills while maintaining full quality assurance.
{% endtab %}
{% endtabs %}

### Use Cases By Persona

<table data-view="cards"><thead><tr><th></th><th data-hidden data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Managers</strong> use cases</td><td><a href="/pages/RgqTkfr9OknkkLo8DWoB">/pages/RgqTkfr9OknkkLo8DWoB</a></td><td><a href="/files/rRQi4XhPlfCE7aHazhxV">/files/rRQi4XhPlfCE7aHazhxV</a></td><td><a href="/pages/avh4ChCHAC9YuqDuZvHI">/pages/avh4ChCHAC9YuqDuZvHI</a></td></tr><tr><td><strong>Developers</strong> use cases</td><td><a href="/pages/nm9WU6AKT7kKZTkzzmHj">/pages/nm9WU6AKT7kKZTkzzmHj</a></td><td><a href="/files/pcphaCu2BsHp45YpHPEG">/files/pcphaCu2BsHp45YpHPEG</a></td><td><a href="/pages/i4EGm5UP3UpXOdRAKXKb">/pages/i4EGm5UP3UpXOdRAKXKb</a></td></tr><tr><td><strong>QA Engineers</strong> use cases</td><td><a href="/pages/egR9ZXbsjDORQ4hO8bR5">/pages/egR9ZXbsjDORQ4hO8bR5</a></td><td><a href="/files/tlpG4V4CM2rCjpbd8Ujj">/files/tlpG4V4CM2rCjpbd8Ujj</a></td><td><a href="/pages/atcmGlpOppAHe15aNFW1">/pages/atcmGlpOppAHe15aNFW1</a></td></tr></tbody></table>