> For the complete documentation index, see [llms.txt](https://cover-docs.diffblue.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cover-docs.diffblue.com/features/cover-optimize/get-started-cover-optimize.md).
# Get started - Cover Optimize
Diffblue Cover Optimize speeds up the time required to run Java unit tests by running only the tests in your project that are relevant to your code change (defined in a patch file). Cover Optimize is provided as a:
* **Gradle Plugin** - The plugin acts as a wrapper around Cover CLI, invoking Diffblue Cover Optimize before the Gradle `Test` task. The plugin calculates the impact of the patch file on your codebase and applies filters to the `Test` task to ensure that Gradle only runs the tests relevant for the changes introduced.
* **Maven Plugin** - The plugin acts as a wrapper around Cover CLI, invoking Diffblue Cover Optimize during `mvn test` or `mvn verify`, and feeding its output into Maven’s Surefire & Failsafe plugins in order to only run the tests exercised by the patch.
Cover Optimize can be used by developers using Cover CLI, reducing wait time and saving workstation loading, but can also be integrated directly into your CI Pipeline (with Cover Pipeline) saving cloud computing costs and optimizing PR workflows.
Prefer video? No problem. Check out our getting started video.
{% embed url="" %}
## Next steps
The configuration required for Gradle and Maven is quite different so please refer to [Cover Optimize & Gradle](/features/cover-optimize/get-started-cover-optimize-and-gradle.md) and [Cover Optimize & Maven](/features/cover-optimize/get-started-cover-optimize-and-maven.md) for getting started information specific to each build tool.
{% hint style="info" %}
Note that Cover Optimize is currently not available for Cover Pipeline for GitLab.
{% endhint %}