Managing Test Project Lifecycle & Status in AXQA

Every project goes through phases. From early setup to active execution and finally closure, the project status reflects where the work stands. Keeping this status accurate helps teams understand priority, ownership, and operational context at a glance.

Why it matters

• Gives immediate clarity about whether a project is active, experimental, or completed.
• Prevents confusion when running Test Campaigns or executing test cases.
• Supports reporting, filtering, and long-term traceability.

When to use it

• You are launching a new project and want to mark it as experimental or demo.
• The project moves into active production testing.
• The project is completed but needs to remain accessible for history and reporting.
• You want to filter dashboards based on active vs closed projects.

Core concepts

• Demo – Initial or experimental phase. Used for setup, proof of concept, or early testing.
• Active – Fully operational. Test cases and Test Campaigns are actively maintained and executed.
• Closed – No longer active. Historical data remains available for reference.
• Lifecycle – The natural progression of a project from setup to completion.

How it works

1. When a project is created, it starts in its initial status (commonly Demo or Active).
2. As work progresses, the status can be updated manually in Project Settings.
3. Active projects allow full operational workflows, including running Test Campaigns.
4. Closed projects remain accessible for reporting but are no longer part of daily execution flow.
5. Status changes apply immediately across dashboards and filters.

How to use it

Step 1: Review current status

Open Project Settings and check the current lifecycle stage.

Step 2: Update status when needed

Change the status based on real operational state:

Use Demo during early configuration or pilot testing.Use Active once regular execution begins.Use Closed when testing work is completed. 

Step 3: Communicate the change

Status updates affect team visibility and planning. Make sure stakeholders are aware when moving a project to Closed.

Best practices

• Keep project status aligned with real operational activity.
• Close projects instead of deleting them to preserve execution history.
• Review lifecycle stage during major releases or client milestones.
• Avoid leaving inactive projects marked as Active.

Common mistakes

❌ Leaving completed projects marked as Active
✔ Move them to Closed to keep dashboards clean and accurate.

❌ Using Demo for long-term production testing
✔ Switch to Active once the workflow becomes operational.

❌ Deleting a project instead of closing it
✔ Close it to preserve test cases, Test Campaign history, and reporting data.

Security & permissions

• Only authorized users can change project status.
• Status updates do not remove historical execution data.
• Closed projects remain protected under the same access rules.

Related documentation

• Creating a Project
• Managing Project Settings
• Test Campaign Overview