Apus has three Vitest suites (unit/integration, e2e, live) plus Docker runners. This page covers what each suite covers, which command to run for a given workflow, how live tests discover credentials, and how to add regressions for real-world provider/model bugs.

QA stack (qa-lab, qa-channel, live transport lanes) is documented separately:

  • QA overview - architecture, command surface, scenario authoring, and the Matrix live lane.
  • Maturity scorecard - how release QA evidence supports stability and LTS decisions.
  • QA channel - the synthetic transport plugin used by repo-backed scenarios.

This page covers the regular test suites and Docker/Parallels runners. QA-specific runners below lists the concrete qa invocations and points back at the references above.

This page is an index. The testing kit is documented on six pages, one per reader job. Open the page that matches your task.

Page Read it when
Test suites and commands You need to pick a suite, a command, or the offline regression checks.
Live and Docker/Parallels workflows You are debugging a real provider or model through a live Docker or Parallels lane.
Docker test runners You want the Docker "works in Linux" lanes, their scheduler, and their env vars.
QA-specific runners You are running a QA Lab lane or need the shared Convex credential contract.
Contract tests You changed a channel, provider, or plugin-sdk surface.
Writing and adding tests You are writing a test, a regression, or a reliability eval.

Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /help/testing#qa-specific-runners still resolves. Each entry points at the page that now holds the content.

Related