Creating a Project

Creating a Test Management Project in AXQA

Create a new Project workspace in AXQA, assign visibility, invite team members, and optionally set an initial Build/Version. Every test case, plan, and API execution happens inside a project.

Why it matters

Structure & isolation: a Project is the boundary for your test assets (APIs, test cases, plans).
Access control: Project Type (Private/Public/Team) + memberships define who can see and work.
Traceability: optional Build/Version helps link executions to the exact release context.

When to use it

You’re starting testing for a new product/game/service or a new client engagement.
You want separate workspaces for environments/teams (e.g., “Game-A”, “Game-A Staging”, “Client-B”).
You need to invite specific testers and control who can access project content.

Core concepts

Project – the main workspace boundary in AXQA
Project Type – Private / Public / Team (visibility scope)
Project Owner – creator of the project; stored as project owner
Team Members – users linked through ProjectMembership
Project Status – demo / active / closed
Build – optional ProjectBuild entry (build number / version / platform) that can become current build

How it works

You open the “Add Project” page and fill in the project fields.
AXQA checks your license limit before creating the project.
The project is saved with you as project owner.
If you entered build/version/platform, AXQA creates a ProjectBuild and sets it as current build.
AXQA creates ProjectMembership for the owner + any invited team members.
Your “Current Project” is updated, so the UI switches to the new project.

How to use it

Step 1: Open Add Project

Go to Projects → Add New Project.

Step 2: Fill the basic fields

Project Name: unique name (max length enforced by the model).
Description: optional (sanitized for safety).
Project Type: Private / Public / Team.
Project Status: demo / active / closed.
Start Date / End Date: optional dates (end date can’t be before start date).

Step 3: Invite team members (optional)

Select users in Team Members. AXQA will create ProjectMembership records for each selected user.

Step 4: Set initial build/version (optional)

If you enter any of these fields, AXQA will create a ProjectBuild and set it as the project’s current build:
Build number (e.g., 0.7.85 / 12345)
Version (e.g., v0.7.85)
Platform (optional, e.g., PC / PS5)

Step 5: Create

Click Create/Save. If you are within the license project quota, the project will be created and you will be redirected to the Projects list.

Best practices

Use clear naming conventions (Client + Product + Env), e.g., “WB-Coop-Staging”.
Set the initial build/version early so executions are easier to filter and audit later.
Use Team type when you want controlled access via memberships rather than “open visibility”.

Common mistakes

❌ Using a non-unique project name
✔ Pick a unique, short name (the system enforces uniqueness).

❌ Setting an end date earlier than the start date
✔ Fix the dates (AXQA validates this in the form).

❌ Forgetting to invite testers
✔ Add them in “Team Members” (memberships are stored in ProjectMembership).

Security & permissions

Inputs are sanitized (Project Name / Description) to reduce XSS risk.
Owner is always recorded as project owner and is also added as a ProjectMembership entry.
Project access and execution are governed by project type + memberships + your permission decorators (documented in “Project Visibility & Access Control”).

AXQA

Did You Know?