01
Create the workspace
Start with the team boundary. Create the workspace and invite only the people who need access to execution, review, administration, or reporting.
OutputTeam-ready workspace
Your First AXQA Workflow
Start structured.
Start structured.
See useful results fast.
Create a workspace, organize your first project, define what should be tested, choose the right execution path, and keep the outcome connected to history and reporting. AXQA guides the workflow without forcing every team into the same testing model.
The guided run on this page uses sample data to explain the onboarding flow.
AXQA Launch Sequence
FIRST WORKFLOW
WorkspaceTeam & access
ProjectScope & structure
TestCases & logic
ExecuteRight path
UnderstandHistory & result
Current focus
Set up your workspace
Step 1 of 5
Create Once
Set up the workspace and project structure your team will reuse.
Choose Your Path
Start manually, through APIs, or through approved Smart Agent execution.
Keep Context
Execution results stay attached to the same test and project history.
Grow Gradually
Begin with one workflow, then expand coverage as your team is ready.
Choose your starting point
Different teams can start differently. The workflow stays connected.
Pick the path closest to what you need today. AXQA keeps the underlying QA record consistent while the execution approach changes around your environment and testing goals.
Recommended first workflow
Run one structured manual test from start to finish.
Create a project, add a small test case, assign it, execute the steps, and review the result in history. This is the fastest way to learn the AXQA operating model before adding more complexity.
Create one project with a clear release or feature scope.
Add one test case with expected behavior and reusable steps.
Execute it and record the result in the same QA workflow.
Manual QA path
Test CaseExpected behavior
ExecuteStep by step
ResultPassed / Failed
HistoryKeep context
One simple execution teaches the same connected workflow you can later scale across projects, APIs, automation, and local environments.
Your first setup
Five steps from empty workspace to useful QA signal.
02
Create one project
Use a real product, release, or service as your first project. Keep the initial scope small enough that your team can understand the complete workflow.
OutputClear QA scope
03
Add the first test
Define the behavior you want to verify. Add steps, expected outcomes, API logic, or other supported validation details that match your chosen workflow.
OutputExecutable test intent
04
Choose execution
Run manually, use supported API execution, schedule the work where appropriate, or route approved private testing through Smart Agent.
OutputRight execution path
05
Read the result
Review the execution outcome, validation context, and history. Then expand only after your first workflow is producing information the team can act on.
OutputConnected QA visibility
Interactive first run
See your first AXQA workflow come alive.
Choose a starting path above, then run the simulation. The sequence changes to reflect the kind of first workflow you selected.
WorkspaceReady
ProjectConfigure
TestDefine
ExecuteManual
ResultConnected
FIRST WORKFLOW
Ready to run
Steps0 / 5
ExecutionNot started
HistoryWaiting
getting-started.axqaSIMULATION
$ Select a path and run your first AXQA workflow.
A good first AXQA rollout
Start with one workflow your team already understands.
Do not begin by migrating every case, automating every path, or connecting every environment. Prove one end-to-end workflow first: define it, run it, validate the outcome, review the history, and confirm the result is useful to the people making QA decisions.
01
Pick a real workflow.Use something the team already knows how to test.
02
Keep scope small.One project and a few representative tests are enough to learn.
03
Validate the result.Make sure AXQA records the information your team actually needs.
04
Expand deliberately.Add more coverage, execution paths, and automation after the first flow works.