Projects

Projects are the main organizational unit in QANode. Each project groups test scenarios (flows), suites, documentation, and executions related to a system, feature, or team.

Creating a Project

1. In the sidebar, click Projects
2. Click + New Project
3. Fill in the fields:

4. Click Create

Image: Project creation modal with all fields filled in

Project Status

To change the status, open the project and use the options in the header:

• Complete → Marks as completed
• Cancel → Marks as cancelled
• Archive → Moves to archived

Project Page

The project detail page has the following tabs:

Overview

Displays statistics and a summary of the project:

• Total Scenarios — Number of test flows
• Total Suites — Number of suites
• Pending/Approved/Failed Scenarios — Scenario statuses
• Recent Executions — List of the latest executions
• Progress — Comparison between elapsed time and executed scenarios

Image: Overview page showing statistics cards, recent executions, and progress bar

Scenarios

Lists all scenarios (flows) in the project:

Actions:

• + New Scenario — Creates a new flow and opens the editor
• Execute — Runs the scenario quickly
• Edit — Opens the flow editor
• Delete — Removes the scenario

In QANode Enterprise, those scenarios can also be executed by pipeline using @qanode/cli with:

• ID
• scenario name + project name

For details, see CI/CD CLI and API.

Suites

Lists the project suites with scheduling information and last result.

For details about suites, see Test Suites.

Variables

The Variables tab lets you create reusable values only inside that project.

Use project variables for data that should not be global, such as environment URL, test users, test data keys, or flags specific to that product.

In scenarios linked to the project, these variables are available in the editor Variables panel and can be used with the same syntax:

{{ variables.VARIABLE_NAME }}

The main Variables menu lists only global variables. Project variables are managed inside the project itself.

Executions

History of all project executions:

Defects — Enterprise

Lists the defects linked to the project. For each scenario in the list you can see if it is blocked by an active defect, with a direct link to the defect responsible for the block.

Available actions in the scenario list:

A scenario blocked by a defect appears with a visual indicator in the list and is counted in the Blocked Scenarios metric in reports.

To open a new defect, use the failed execution of the scenario or go directly to the Bugs tab in the sidebar.

Documentation

Project file management:

• Upload — Upload documents (requirements, specifications, etc.)
• Download — Download attached documents
• Delete — Remove documents

When using MCP, project documents can be read by an AI client to help create or review scenarios. QANode supports text PDFs, scanned PDFs/images with OCR, DOCX, TXT, JSON, CSV, XLSX previews, and metadata from other files. For large PDFs, it is usually better to read specific pages or page ranges.

When scenarios in the project are created or updated through MCP, the project scenario list receives the same realtime updates used by the QANode interface.

Filtering and Search

In the project list, you can:

• Search by name — Search field at the top
• Filter by status — Filter dropdown (Active, Completed, etc.)

Duplicate Project

To create a copy of an existing project:

1. In the project list, click the options menu (⋮) for the project
2. Select Duplicate
3. A new project will be created with the same scenarios

Tips

• Use status to track the project lifecycle
• Archive old projects to keep the list clean
• Start and end dates help track progress vs. planning
• Use the Documentation tab to keep requirements and specifications alongside the project