# Maintain Your Test Suite

Kerno keeps your test suite in sync with your project without any manual work. Once a baseline exists, Kerno watches how your code evolves and updates the tests accordingly.

<figure><img src="https://3940381227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuNjVcN7yphTDowu96vxO%2Fuploads%2Fl4SaFyJsTjZkWukzbf3q%2Ftest%20Update_docs.gif?alt=media&#x26;token=317bfbd3-3d68-4313-8057-94ba9cd6bfef" alt=""><figcaption></figcaption></figure>

### How Maintenance Works

{% stepper %}
{% step %}

#### **Analyze your updated code**

<mark style="color:$info;">Kerno reviews the changes in your project to understand how the endpoint has shifted.</mark>
{% endstep %}

{% step %}

#### **Run existing scenarios**

<mark style="color:$info;">Kerno executes your scenarios and compares the results with the saved baseline.</mark>
{% endstep %}

{% step %}

#### **Surface behaviour differences**

<mark style="color:$info;">Any changes in behaviour are shown clearly so you can review them.</mark>
{% endstep %}

{% step %}

#### **Apply accepted changes**

<mark style="color:$info;">If you accept the differences, Kerno updates the scenarios to match the new behaviour.</mark>
{% endstep %}

{% step %}

#### **Add/remove scenarios**

<mark style="color:$info;">Kerno checks whether new scenarios should be created or old ones removed.</mark>
{% endstep %}

{% step %}

#### **Keep everything aligned**

<mark style="color:$info;">Your test suite stays consistent with your current code without any manual work.</mark>
{% endstep %}
{% endstepper %}

You do not need to rewrite old tests, fix broken scenarios, or manage fixtures. Kerno handles all ongoing adjustments and keeps the entire suite accurate as your project evolves.

{% hint style="info" %}
If you encounter issues or have questions, [message us on Discord](https://discord.gg/k8yA9tZdP9), and we’ll gladly help.
{% endhint %}