Skip to content

feat(inspire-config): write the test report of every Jest, Vitest and pytest check - #153

Merged
IreneGonPa merged 4 commits into
release/2026-11-19from
feat/inspire-config-test-reports
Nov 20, 2026
Merged

IreneGonPa merged 4 commits into
release/2026-11-19from
feat/inspire-config-test-reports

Conversation

@IreneGonPa

@IreneGonPa IreneGonPa commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Jira INSPIRE-31. Releases together with INSPIRE Factory Genomcore/inspire-factory#211: neither ships without the other.

Why

INSPIRE Factory's 091-test-reports makes a unit pass only when the tests that cite its claims ran and passed, which it reads from each test check's JSON report. A run whose plan has units with claims does not start when no test check of .inspire/emanate.yml declares a report. Today /inspire-config writes none, so every project it configures would stop. That Factory release raises its INSPIRE floor to the version that carries this change: 0.21.0, since 0.20.0 shipped on 2026-11-19 without it. INSPIRE names no Factory version.

Change (plugin/base/skills/inspire-config/)

  • references/derive.md:
    • report is on by default, like run_related, for every Jest, Vitest or pytest check in phase tests, e2e suites included.
    • The reporter flags go in run and run_related: Vitest --reporter=default --reporter=json --outputFile.json=<file>, Jest --json --outputFile=<file>, pytest --json-report --json-report-file=<file>. pytest needs pytest-json-report, which the skill proposes adding.
    • The file is .inspire-report-<check>.json in the command's directory, and report names it from the repository root. .gitignore covers .inspire-report-*.json.
    • Other runners get no report, and the skill says that a run with claims will not start.
    • "Updating an existing file" proposes report for a check without one.
    • Jest and Vitest e2e checks get run_related with {tests} (the test files that cite the unit's claims; Jest --runTestsByPath {tests}, Vitest vitest run … {tests}), and an e2e run_related with {files} is proposed to switch. An e2e test seldom imports the file a unit changes, so under {files} it never runs in the unit and its citations would never count.
  • references/format.md: run_related accepts {files} or {tests}, with what {tests} becomes and the Jest and Vitest forms; report in the run-check keys with the Factory's errors, a "Test reports" section (what the Factory does with the report, that a test run_related does not select never counts in the unit, and the run-start error), and the example with a report on both test checks and {tests} on the e2e one.
  • references/validate.md:
    • errors: a test check without report; a report its commands do not write; pytest without pytest-json-report;
    • warnings: a report that .gitignore does not cover; an e2e run_related with {files}.
  • SKILL.md: report leaves the list of keys never written, and is written by default, like run_related.

/inspire:update needs no change: its Step 10 already runs /inspire-config review, which now reports a test check without report and offers /inspire-config init.

For the release

  • This needs the next minor, 0.21.0 (the Factory's floor). Its changelog goes under Breaking for existing vaults: after /inspire:update, run /inspire-config init to add report to the test checks, or a run of the new Factory with claims does not start.
  • Merge this and #211 together.

Verification

  • bash plugin/test/run.sh: 111 of 112 files pass (2187 assertions). The one failure is visor/01-graph-plugin.sh, case "an unreachable registry with a cold npm cache exits 3": it builds the visor's graph plugin against npm, reads nothing of this skill, and depends on the local network.
  • The Factory side was checked against these exact flags: Vitest 4.1.8 writes the report with --reporter=json --outputFile.json=…, also from vitest related --passWithNoTests with no related test, and the Factory's reader parses it.

🤖 Generated with Claude Code

… pytest check

INSPIRE Factory now reads each test check's JSON report, and a run whose
plan has units with claims does not start when no check declares one.
/inspire-config writes `report` by default, like run_related: the reporter
flags in run and run_related (Vitest --reporter=json, Jest --json, pytest
--json-report) and the path `.inspire-report-<check>.json` from the root.
Updating a file proposes the same for a check without one, and validation
flags a missing or mismatched report, pytest without pytest-json-report,
and a .gitignore that does not cover it. INSPIRE names no Factory version:
the Factory declares the INSPIRE floor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions
github-actions Bot changed the base branch from release/2026-11-18 to release/2026-11-19 November 19, 2026 09:09
@github-actions

Copy link
Copy Markdown
Contributor

Reapuntada de release/2026-11-18 a release/2026-11-19, la release abierta. A main solo se llega desde release/, hotfix/ o docs/.

IreneGonPa and others added 3 commits November 19, 2026 15:40
…cks ran

The Factory no longer adds the citing tests to run_related's files: that
is what `{tests}` does. Say instead that a test run_related does not
select never counts in the unit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An e2e test seldom imports the file a unit changes, so with {files} its
citations never count in the unit. /inspire-config now writes run_related
with {tests} on Jest and Vitest e2e checks, and proposes it on update.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@IreneGonPa
IreneGonPa merged commit adef4ab into release/2026-11-19 Nov 20, 2026
6 checks passed
@IreneGonPa
IreneGonPa deleted the feat/inspire-config-test-reports branch November 20, 2026 06:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants