Add the Testing tool Jest reporter (@ai-testing-tool/forge-jest) in jest.config so each Jest run can publish results and autogenerate TestCases on ingest. Pair it with a CI snippet from the template builder.

This reporter does not replace Test Design. Design you edit in Jira stays on the TestCase; a new launch clones a snapshot onto a TestExecution.

Install

npm install -D @ai-testing-tool/forge-jest @ai-testing-tool/forge-commons

Package guide: qa-jest.

Configure

In jest.config.js:

reporters: [
  'default',
  ['@ai-testing-tool/forge-jest', { /* mode / projectKey optional */ }],
],

Set AI_TESTING_TOOL_MODE=ingest plus project key, ingest URL, and token when the run should upload. Default mode is off. file writes an ingest payload locally.

Prefer Jira issue keys in test titles. Use qa helpers from @ai-testing-tool/forge-jest/jest. Run with --runInBand when you rely on those helpers so they share the reporter bridge.

In Jira

  1. Connect ingest.
  2. Open Apps → Jest. Follow Open guide, or Setup with Jest preselected.
  3. Run Jest with AI_TESTING_TOOL_MODE=ingest after your test stage.

Optional Path A: npx jest --json --outputFile=… plus the CLI upload. Prefer the reporter unless you already have that JSON pipeline.

FAQ

Did ingest overwrite the steps I wrote in Test Design?
A new launch clones design onto a new TestExecution. Re-sync of the same launch does not re-clone.