Cloning a Project

Project Cloning allows you to create a new project using the structure and supported configuration of an existing AXQA project.
It is designed to reduce repetitive setup work while keeping the new project separate from the original.

Why it matters

• Saves time when multiple projects use a similar QA structure.
• Reduces manual configuration and setup errors.
• Makes it easier to create controlled project copies for new products, releases, clients, or testing scopes.

When to use it

• When creating a new project based on an existing QA structure.
• When starting a similar project for another product or client.
• When preparing a separate project for a new testing scope.
• When you want to reuse existing test assets without rebuilding them manually.

Core concepts

• Source Project – The existing project used as the basis for the clone.
• Cloned Project – The new independent project created by the cloning process.
• Project Structure – The supported configuration and testing assets copied from the source.
• Execution History – Historical execution data that may be optionally included when supported.
• Sharing Data – Share links, verification information, sessions, and related external-access data.
• Independent Project – A cloned project that can be managed separately after creation.

How it works

1. Select the source project.
2. Start the Clone Project action.
3. Define the new project information.
4. Choose the optional historical or sharing data to include, when available.
5. AXQA creates the new project.
6. Supported project structure and testing assets are copied.
7. The cloned project becomes independent from the source project.

How to use it

Step 1: Select the source project

Choose the project containing the structure you want to reuse.

Before cloning, review the project and confirm that its configuration is appropriate for the new project.

Step 2: Start the cloning process

Use the Clone Project action from the supported project management interface.

Enter the requested information for the new project.

Use a clear name that distinguishes the cloned project from the source.

Step 3: Review what should be copied

AXQA may copy supported project information and testing assets such as:

• Project configuration
• Team membership information
• Builds
• API definitions
• API parameters
• Test Cases
• Test Steps
• Test Plans and Campaign structures
• Automation rules
• Supported AutoCase data
• Supported Staffing AI data
• Supported comments and task-related data

The exact copied data depends on the information available in the source project and the supported AXQA clone operation.

Step 4: Review optional historical data

Where available, AXQA may provide options for copying additional historical information such as:

• Execution Logs
• Share Audit Logs

Only include historical information when it is useful for the new project.

For a clean project start, leave unnecessary history excluded.

Step 5: Review sharing-related options

Sharing-related information may include sensitive access data such as:

• Share Links
• OTP-related data
• Sharing Sessions

Sensitive sharing information is excluded by default unless the available clone option is explicitly selected.

Only copy this information when there is a clear business requirement.

Step 6: Create the cloned project

Confirm the clone operation.

AXQA creates a new project using the selected source project information.

The new project is independent and can be managed separately after creation.

Step 7: Review the new project

After cloning, review the new project before using it for active testing.

Check:

• Project information
• Team membership
• Builds
• Tests
• APIs
• Test Plans
• Automation
• Sharing configuration
• Current Project context

Remove or update anything that should not remain in the cloned project.

Best practices

• Review the source project before cloning it.
• Use cloning for reusable structure, not as a substitute for proper project organization.
• Give the new project a clear and unique name.
• Exclude historical execution data unless it provides value to the new project.
• Keep sensitive sharing data excluded unless it is specifically required.
• Review all cloned tests, APIs, builds, and team assignments before execution.
• Validate the cloned project with a small test before starting full execution.

Common mistakes

❌ Assuming the cloned project stays synchronized with the source project.
✔ The clone is an independent project after creation.

❌ Copying historical data that is not relevant to the new project.
✔ Include historical information only when it has a clear purpose.

❌ Copying sensitive sharing information automatically.
✔ Keep sharing-related data excluded unless it is specifically required.

❌ Starting execution immediately after cloning.
✔ Review the cloned configuration and run a small validation first.

Security & permissions

• AXQA checks project access before allowing supported project-management operations.
• Cloning does not automatically grant users additional permissions.
• Sensitive sharing information is excluded by default unless explicitly selected.
• Review Team membership and project visibility after cloning.
• Do not reuse external-access information unless the same access is intentionally required for the cloned project.
• Treat cloned projects as separate security boundaries after creation.

Related documentation

• Project Overview
• Creating a Project
• Current Project: Activate, Switch & Pause
• Project Visibility & Access Control
• Project Membership & Access Roles
• Managing Builds, Versions, Environments & Platforms
• Deleting a Project Safely