Skip to main content
The QAOS dashboard includes a guided config builder that generates a valid qaos-config.json for you. This is the fastest way to set up a new run, especially if you’re not familiar with the JSON format.

​
Accessing the builder

  1. Log in to the QAOS Dashboard
  2. Navigate to Projects and open or create a project
  3. Click New Run → Configure with UI

​
Step 1 — Name your run

Enter a descriptive name for this run. This name appears in your run history and reports, so make it identifiable: 
Production audit — March 2025
Login flow security check
Post-deploy accessibility review

​
Step 2 — Add tasks

Click Add Task to define each test scenario. For each task, fill in:
1

Task description

Describe what the agent should do in natural language. Be specific about the user flow and what you want tested.Example: "Navigate to the checkout page, add an item, and proceed through the payment flow"
2

Start URL

Enter the URL where the agent should begin this task. This should be the most relevant entry point for what you want tested.Example: https://your-app.com/shop/cart
3

Agents to run

Toggle the Security and/or Quality agent for this task. Both are enabled by default.
  • Security — checks for vulnerabilities, access control issues, weak cryptography, etc.
  • Quality — checks for accessibility violations, UX issues, navigation problems, etc.
Repeat for each distinct area of your application you want to test.

​
Step 3 — Review and export

Once you’ve added all tasks, click Preview JSON to see the generated config file. You can:
  • Copy to clipboard — paste it into a file on your machine
  • Download — save it directly as qaos-config.json
  • Run directly — start the run immediately from the dashboard (requires the CLI to be running and connected)

​
Editing the generated config

The exported JSON is a standard QAOS config file. You can edit it freely — add more tasks, adjust descriptions, change agent selections, or add environment file references. See the JSON Reference for a complete field description.

​
Tips for good configs

Cover the full user journey. Create one task per major feature area: authentication, user profile, data listings, admin panels, checkout flows, etc.
Include authentication context. If your application requires login, add an authentication task first (e.g., “Log in with admin@example.com / password123”) before tasks that test authenticated pages.
Only test applications you own or have permission to test. See Terms of Use for the full policy.