---
title: Projects
slug: suite-documentation/projects
docTags: 
createdAt: 2025-11-16T16:32:33.463Z
---

## Overview

A **Project** represents your test automation code within Testinium Suite.

It is the starting point of the workflow and acts as the container where your test code is connected, structured, and prepared for execution.

Each Project is created with a specific **framework type** (e.g., Selenium, Appium, Service), which determines how your test code is interpreted and executed.

All Scenarios are discovered from a Project, and all Plans operate within its scope.

Before creating Scenarios or Plans, a Project must exist.

## How It Works

A Project connects your test repository to the platform and defines how your test code should be executed through its selected framework.

Once created, the system:

- Accesses your test code 
- Interprets it based on the selected framework 
- Scans the project structure 
- Identifies executable test units 
- Makes them available as **Scenarios** 

This means your test logic remains in your codebase, while execution and orchestration are handled by the platform.

### Project List

On the main Projects screen, you can:

- View all existing Projects
- Search Projects using the search bar
- Sort Projects (e.g., recently added)
- Create a new Project

Each Project card includes:

- **Project Name**
- **Framework Type** (e.g., Selenium, Service)
- **Creation Date**
- Quick access buttons:
  - **Summary**
  - **Scenarios**
  - **Plans**
  - **Code Compatibility**
- **Clone** option
- Additional actions (via menu)

### Create New Project

To create a new Project, click **Create New Project**.

You will first select the project type:

- **Selenium** → Seleinum 3 Web browser testing
- **Appium **→ Appium 1 Mobile testing
- **Appium 2** → Appium 2 Mobile testing
- **Service** → API / service testing
- **Selenium 4 (Beta)** → Seleinum 4 Web browser testing

This selection determines how your test code will be executed and which configurations are required.

Detailed steps and configuration options are explained in the **Create New Project** documentation.

## Repository Usage

Projects rely on a repository to access test code.

By default, the platform provides a repository structure.
Alternatively, you can use your own repository.

Custom repositories can be configured at:

**Account → Company → Custom Git Repository**

Once configured, Projects use this repository connection for test code access.

### Using a Custom Repository

You can configure a custom Git repository at the **Company level**.

Path:
 **Account → Company → Custom Git Repository**

When enabled:

- You can provide your own repository URL 
- Authentication (username and password) can be defined 
- All Projects can use this repository configuration 

This allows you to:

- Connect private repositories 
- Use your own version control setup 
- Maintain full control over your test code 

If a custom repository is not configured, the system uses the default repository structure provided by the platform.

### Key Behavior

- The Project acts as the **source of truth** for test discovery
- Only code inside the defined repository folder is scanned
- Scenario detection depends entirely on this structure

## Code Compatibility

Each Project includes a **Code Compatibility** feature.

This feature analyzes your test code to determine whether it is compatible with the platform’s execution environment.

It helps identify:

- Missing dependencies
- Unsupported configurations
- Structural issues in the project

## Clone Project

Projects can be cloned to quickly replicate configurations.

Cloning allows you to:

- Reuse existing setup
- Create variations of a Project
- Avoid reconfiguring repository and structure

## Key Principles

- A Project must be created before Scenarios or Plans
- Project type determines framework & execution behavior (Appium, Selenium etc.)
- Repository structure directly affects Scenario detection
- All Scenarios and Plans operate within a single Project
- The platform executes your code as-is, based on Project configuration