@devant-net/vitest-reporter

Vitest custom reporter that streams test runs into Devant Cloud.

Install

npm i -D @devant-net/vitest-reporter
# or
bun add -d @devant-net/vitest-reporter

Configure

Set the connection in env or in vitest.config.ts:

// vitest.config.ts
import { defineConfig } from "vitest/config";

export default defineConfig({
  test: {
    reporters: [
      "default",
      ["@devant-net/vitest-reporter", {
        apiUrl: "https://<tenant>.devant.net",
        apiToken: process.env.DEVQ_TOKEN,
        projectId: 7,
      }],
    ],
    coverage: { reporter: ["v8"] }, // optional — surfaces in Devant Cloud
  },
});

Or pure env:

DEVQ_API_URL=https://<tenant>.devant.net \
DEVQ_TOKEN=dq_ci_lv_... \
DEVQ_PROJECT_ID=7 \
  vitest run

What gets reported

| Vitest event | Devant Cloud action | | ------------------ | ------------------------------------------------------------ | | onTestRunStart | POST /v1/runs — create the run, capture CI metadata | | onTestCaseResult | POST /v1/runs/:id/results — per-test attempt, retries | | onCoverage | POST /v1/runs/:id/coverage — v8 / istanbul summary | | onTestRunEnd | POST /v1/runs/:id/complete — stamp finished_at |

Snapshot mismatches surface the diff text in error_message. Retries land as separate test_result_attempt rows under the same test.

Test-case identity

When a result arrives, the reporter resolves it to a test_case in this order:

1. @DEF-AB12 style tag on the test (test("logs in @DEF-AB12", …))
2. Exact fullName match in the project
3. Auto-create a new test_case (the reporter prints a @KEY hint you can paste back into source to lock the binding)

Orchestrated runs

If DEVQ_RUN_ID is set, the reporter attaches to that existing run instead of creating its own. The orchestrator owns createRun / completeRun; this reporter only streams results.

License

See LICENSE.