Skip to content
CertiQA LogoCertiQA LogoCertiQA Docs
CertiQA is in early access. Request access

Getting Started with CertiQA

Understanding the project hierarchy, setting up workspaces, and executing your first test on the visual canvas.

How CertiQA Organizes Your Work

Section titled “How CertiQA Organizes Your Work”

Every piece of testing content in CertiQA sits inside a five-level hierarchy: Organization → Projects → Test Suites → Test Cases → Test Steps. An Organization is your whole company or team account; a Project is usually one application or one agent under test (a web app, a customer-facing chat agent, a REST API); Suites group related Cases for a purpose (Smoke, Regression, Nightly); and each Case is a sequence of Steps that actually click, call, or converse. The detail that saves the most maintenance work later is that a Test Case is not owned by a single Suite – the same Case can be assigned to Smoke and Regression and a release-gate Suite at once, so a critical checkout flow only has to be written once and still shows up everywhere it needs to run.

Without this separation, teams typically end up copy-pasting the same login-and-navigate steps into every suite that needs them, and a single selector change means hunting down and fixing five near-duplicate copies. CertiQA’s hierarchy, combined with CertiBlocks™ (reusable sub-routines covered in the Reusability guides) for the steps themselves, is what keeps a Case-level fix a one-place edit instead of a search-and-replace across the whole Project.

Finding Your Way Around the App

Section titled “Finding Your Way Around the App”

The Customer App is a single-page application, so almost everything you do lives behind the left sidebar and a Project switcher in the top-left – there is no separate admin console to jump between. Before you go looking for a specific surface, it helps to know what each sidebar destination actually is: Test Suites is where you organize and run everything described above; CertiMind Studio is the AI Copilot that can draft a first pass of test steps for you from a live snapshot of your target page or API, which you then review and edit rather than writing from a blank canvas; CertiBlocks is the library of reusable sub-routines (a shared login flow, a checkout, an OAuth handshake) that any Case can pull in without re-authoring the same clicks; Run Reports holds the history and evidence (screenshots, network waterfalls, trace DAGs) for everything that has ever executed; and Settings is where BYOK model keys, Vault-stored credentials, and private-deployment configuration live.

Creating and Running Your First Test Case

Section titled “Creating and Running Your First Test Case”
  1. {“title”:“Step 1: Create a Test Suite”,“text”:“From Test Suites, click "+ New Suite" and give it a purpose-revealing name (e.g. "Checkout Smoke"). A Suite is just a named grouping – you will assign Cases to it, not author steps directly inside it.”}
  2. {“title”:“Step 2: Add a Test Case”,“text”:“Open the new Suite and add a Case. For a web app target this opens the Visual Step Builder canvas; for an AI agent target choose an AI Agent Suite instead, which opens the Step Canvas described in 1.1 Composing AI Agent Tests Visually.”}
  3. {“title”:“Step 3: Add steps by hand or let CertiMind draft them”,“text”:“Click "+ Add Step" to build the sequence yourself, or open CertiMind Studio and point it at your target page or endpoint to generate a first draft of steps you can then edit – CertiMind speeds up the first pass, it does not replace reviewing what it produced.”}
  4. {“title”:“Step 4: Run the Case and read the report”,“text”:“Click "▶ Run Case". CertiQA executes every step against your target, and the resulting Run Report captures a pass/fail per step along with the evidence (screenshots, DOM state, or agent transcript, depending on the target type) needed to debug a failure without re-running it.”}