CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

systematic-test-matrix

Run the full POSCursor verification matrix with timestamped evidence under tmp/systematic-test-matrix/. Use for release readiness, pre-deploy QA, or when the user asks to systematically run all test surfaces (tsc, expo-doctor, Jest buckets, full Jest, Playwright, web export, export smoke). Not for authoring individual unit tests — use the testing skill for that.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Systematic Test Matrix

Run POSCursor verification surfaces in a fixed order. Keep evidence in tmp/systematic-test-matrix/<timestamp>/. Never claim green from stale logs.

When to use

NeedAction
Release / deploy confidenceThis skill
Author or fix one Jest filetesting skill
Deploy to Cloudflare after greendeploy-poscursor
Fast iterationnpx jest <path> --no-coverage only

Quick start

  1. Confirm cwd is the POSCursor repo root (posCURSORv2 / this workspace).
  2. Run:
node .agents/skills/systematic-test-matrix/scripts/run_matrix.mjs
  1. Open the newest tmp/systematic-test-matrix/<timestamp>/summary.json and any failing *.log before reporting results.

Workflow (script order)

1. Baseline (bail on failure by default)

  • npx tsc --noEmit
  • npx expo-doctor

2. Jest by discovered __tests__ buckets

The script walks app/ and src/, finds __tests__ dirs with *.test.* files, and runs each with:

npx jest --runInBand --forceExit --runTestsByPath <files…>

Buckets are written to jest-buckets.json in the report dir. Typical buckets include services, utils, components, hooks, models, store(s), cic, and role screens under app/(admin), app/(cashier), app/(borrower), etc.

3. Integrated surfaces

  • jest_full — npm test -- --runInBand --forceExit (catches tests outside __tests__/ folders, e.g. *.regression.test.ts)
  • playwright_full — npx playwright test --workers=1 --reporter=list (skipped with --skip-playwright)
  • export_web — npm run export:web (script uses this, not export:web:production)

4. Export smoke (default on)

Serves dist/ on localhost, opens Chromium, fails on page/console errors. Writes smoke.json. Skip with --skip-smoke.

Commands

# Full matrix
node .agents/skills/systematic-test-matrix/scripts/run_matrix.mjs

# Debug without long E2E / smoke
node .agents/skills/systematic-test-matrix/scripts/run_matrix.mjs --skip-playwright --skip-smoke

# Resume one step
node .agents/skills/systematic-test-matrix/scripts/run_matrix.mjs --only=playwright_full
node .agents/skills/systematic-test-matrix/scripts/run_matrix.mjs --only=jest_full,export_web

# Collect all failures (no early exit)
node .agents/skills/systematic-test-matrix/scripts/run_matrix.mjs --no-bail

Outputs

ArtifactMeaning
summary.jsonPer-step ok/exitCode/logPath; overall ok
jest-buckets.jsonDiscovered buckets for that run
*.logFull command output
smoke.jsonExport smoke URL/title/errors

Agent reporting rules

  1. Quote the report directory path used.
  2. For failures: step name, exit code, log path, first actionable error.
  3. Do not mark release-ready if summary.ok is false.
  4. Optional extra gates (lint, production export, sync integrity) are not in the default script — see references/test-surfaces.md and deploy-poscursor when shipping.

Related

  • Unit/integration authoring: ../testing/SKILL.md
  • Deploy gates: ../deploy-poscursor/SKILL.md
  • Surface catalog: references/test-surfaces.md
Repository

zazakia/JetFarm

Path

.agents/skills/systematic-test-matrix/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.