Your First AXQA Workflow

AXQA brings your QA workflow into one connected system, from project setup and test definition to execution, validation, and results.
Start with one small, real workflow, confirm that everything works as expected, and expand your QA coverage from there.

Why it matters

Helps you understand how the main AXQA components work together.
Lets you validate your setup before creating a large test repository.
Gives your team a structured path from test definition to execution evidence.

When to use it

When you are using AXQA for the first time.
When starting a new QA workspace or project.
When onboarding a new team or introducing a new testing workflow.

Core concepts

Workspace – Your AXQA environment where projects, users, testing assets, and execution history are managed.
Project – The operational boundary that keeps testing scope, people, builds, test assets, and execution context connected.
Test – A definition of what should be validated and how it should be executed.
Execution – The actual validation of a test through a supported AXQA execution method.
Evidence – The results, logs, statuses, and related information generated during execution.
Current Project – The project currently selected as your active working context.

How it works

Access your provisioned AXQA workspace.
Create your first project.
Define one small test or validation workflow.
Choose the appropriate execution method.
Run the test.
Review the result and available execution evidence.
Expand the workflow with additional tests, plans, APIs, automation, or Smart Agent execution.

How to use it

Step 1: Access your AXQA workspace

After your subscription is completed and your dedicated workspace has been provisioned, use the access details provided by AXQA to log in.

Your workspace is the central environment where your QA projects, users, testing assets, and execution activity are organized.

Step 2: Create your first project

Create a project for the product, application, service, or testing scope you want to validate.

Keep the first project simple and use a clear project name and description.

If applicable, define the initial build, version, environment, and platform.

Step 3: Start with one real test

Avoid importing or creating a large number of tests immediately.

Create one small test that represents a real validation your team performs today.

This makes it easier to confirm that your project structure and execution workflow are correct.

Step 4: Choose how to execute

AXQA supports different testing workflows depending on what you need to validate.

You may start with:

Manual Testing – For structured human validation.
API Testing – For API and backend validation.
Smart Agent Execution – For testing systems that require controlled access to local or private environments.
Scheduled Automation – For tests that should execute automatically according to a defined schedule.

Choose the execution method that matches the system and validation you are working with.

Step 5: Execute and validate

Run the test and review its result.

Confirm that the expected information is available, including execution status, history, logs, and other evidence supported by the selected testing method.

Step 6: Expand your workflow

Once the first workflow is working correctly, expand gradually.

You can add:

Additional Test Cases
Test Plans
API definitions
Builds and environments
Team members
Smart Agent connections
Scheduled executions
Reporting and execution history

Build the workflow around real QA needs instead of creating unnecessary structure in advance.

Best practices

Start with one real workflow before creating a large test repository.
Keep project names, builds, environments, and test names clear and consistent.
Confirm the complete execution flow before adding automation.
Use the execution method that matches the system being tested.
Keep testing evidence connected to the correct project and build context.
Expand your AXQA structure gradually as your QA process grows.

Common mistakes

❌ Creating hundreds of tests before validating the first workflow.
✔ Start with one small test, execute it successfully, and expand from there.

❌ Creating tests under the wrong project.
✔ Confirm the Current Project before creating or executing testing assets.

❌ Automating an unstable or unclear testing process.
✔ Validate the workflow manually first, then automate when the process is understood.

❌ Mixing environments or builds without clear identification.
✔ Use consistent build, version, environment, and platform information.

Security & permissions

AXQA applies access controls based on project visibility, membership, ownership, and user permissions.
Seeing a project does not automatically grant permission to manage or execute it.
Smart Agent execution should only be configured for systems and environments your organization is authorized to test.
Keep account access and project membership limited to users who need them.
Always confirm the Current Project before performing sensitive or destructive project operations.

AXQA

Did You Know?