---
title: Code Compatibility
slug: suite-documentation/code-compatibility
docTags: 
createdAt: 2025-12-30T08:20:55.688Z
---

# Overview

The Code Compatibility feature analyzes your project's test automation code and verifies whether it meets the execution requirements of Testinium Suite. This analysis highlights issues that may prevent your tests from running correctly and provides guidance on how to resolve them.

Code Compatibility is especially useful when you are onboarding a new project, modifying your automation structure, or ensuring that your framework setup aligns with Testinium Suite rules.

## Purpose

Testinium Suite enforces certain requirements so that test automation projects can be executed reliably in distributed environments. Code Compatibility checks your repository and evaluates:

- Required folder structures 
- Supported language or framework configurations 
- Dependency requirements 
- File and naming conventions 
- Unsupported patterns or build configurations 
- Elements that may block execution inside Testinium Suite 

The goal is to help you identify potential issues early so you can correct them before running tests.

## When to Use

Use this feature when:

- You push a new project to Testinium for the first time 
- You update your test automation framework or dependencies 
- Your execution fails due to structural or configuration issues 
- You want to verify that your code follows Testinium rules 
- You manage multiple teams and want a consistent project layout

# How to Use

To begin, open the **Projects** page and click the **Code Compatibility** button for the project you want to analyze.

:::hint{type="info"}
The project must be written in **Gauge** for compatibility checks to run. Other frameworks are not supported for this feature.

We plan to support **Cucumber** in the near future.
:::

Inside the **Code Compatibility** tab, click **Start New Analysis** to initiate the process. The analysis may take a few minutes depending on the size of the repository.

All ongoing or completed analyses are listed in the **Analysis History** table.

You can **Refresh **the table and check whether the analysis has finished.

When the analysis is complete, click **View Details** on the relevant row in the table to open the results. The details page will display detected errors, warnings, and their details in the table.

# Status Descriptions

| **Category** | **Status**      | **Description**                                                                                                |
| ------------ | --------------- | -------------------------------------------------------------------------------------------------------------- |
| **Progress** | **In Progress** | The analysis is currently running.                                                                             |
| **Progress** | **Finished**    | The analysis has completed successfully.                                                                       |
| **Progress** | **Failed**      | The analysis could not be completed. Running a new analysis is recommended.                                    |
| **Result**   | **Passed**      | The project meets compatibility requirements and no errors were detected.                                      |
| **Result**   | **Warning**     | The project is compatible, but important items require attention to maintain reliable execution.               |
| **Result**   | **Error**       | Significant findings impact compatibility. Review these items to prepare the project for successful execution. |
| **Result**   | **Failed**      | The project is not eligible for analysis due to unsupported structure or configuration.                        |

# Duration Definitions

**Analysis Time**
Represents the time spent actively running the compatibility scan on your project. This value reflects only the analysis phase.

**Total Time**
Represents the full duration of the process, which includes queue time, preparation steps, the analysis phase, and the finalization stage.