Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

test

Estrellas1

Forks0

Actualizado10 de junio de 2026 a las 09:48

Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

rhanka

rhanka/sentropic

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	test
description	Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.

harness/test

Native sentropic testing discipline (NOT "tdd" ritual — the act is test). Open it with harness test [<scope>] [--category unit|integration|e2e] [--watch] (records a WorkEvent), then follow the loop.

Pyramid

70% unit · 20% integration · 10% e2e. Test behaviour, not implementation — query by user-visible elements (text/role/label) over test ids. Names: "should when ".

Scoped-test loop (while developing)

Run ONLY the test under evolution, on a dedicated test ENV — never dev:

API: make test-api-<suite> SCOPE=tests/<file>.spec.ts ENV=test-<slug>
UI: make test-ui SCOPE=tests/<file>.spec.ts ENV=test-<slug>
E2E: make test-e2e E2E_SPEC=tests/<file>.spec.ts API_PORT=… UI_PORT=… MAILDEV_UI_PORT=… ENV=e2e-<slug>

Full gates only at end of lot/branch: make test-api, make test-ui, make clean test-e2e.

Environment isolation (MANDATORY)

NEVER run test campaigns on ENV=dev — afterEach hooks purge real data.
Branch tests live in the isolated worktree on ENV=test-<slug> / ENV=e2e-<slug>; ENV is the LAST make argument.
NEVER add timeouts to make a flaky e2e pass — a timeout failure is a real bug (bad selector, race, regression). UI waits are <2s except AI generation.

AI-flaky allowlist (non-blocking)

Only accept non-systematic provider/network/model nondeterminism, and only with ≥1 success on the same commit + command. Record the exact command + failing file + failure signature in BRANCH.md and get explicit user sign-off before merge. Everything else is blocking.

CI is authority

CI was green on main → any branch failure IS a branch problem; never claim "pre-existing". Decide: evolution (adapt the test) or regression (fix the code). Local-green / CI-red → trust CI.

Más de este repositorio

mismo repositorio

adopt

rhanka/sentropic

Use when bringing the harness method to a NEW or non-sentropic repo — maps the repo's conventions into a harness profile so the same scope/branch/verify kernel applies anywhere.

2026-06-101

brainstorm

rhanka/sentropic

Use before any creative/design work (a feature, a package, an evolution) — explores intent and design via the spec-ladder with multi-peer adversarial review BEFORE implementation.

2026-06-101

debug

rhanka/sentropic

Use on any bug, test failure, or unexpected behaviour BEFORE proposing a fix — runs the generic evidence-first root-cause loop.

2026-06-101

plan

rhanka/sentropic

Use when you have a spec/decisions and need an executable plan — writes a lot-based BRANCH.md from the template and completes with track for realization state.

2026-06-101

review

rhanka/sentropic

Use when completing a feature, a design step, or before merging — runs a ≥2-peer consensus review and reconciles the findings, instead of a single rubber-stamp pass.

2026-06-101

using-harness

rhanka/sentropic

Load FIRST in any sentropic repo — establishes the harness method (branch/scope/test/debug/review/brainstorm/plan) and supersedes superpowers for those acts.

2026-06-101

name	test
description	Use when adding or evolving tests for a feature/bugfix — applies the sentropic test-pyramid, scoped-test loop, environment isolation, and AI-flaky policy.

harness/test

Pyramid

70% unit · 20% integration · 10% e2e. Test behaviour, not implementation — query by user-visible elements (text/role/label) over test ids. Names: "should when ".

Scoped-test loop (while developing)

Run ONLY the test under evolution, on a dedicated test ENV — never dev:

API: make test-api-<suite> SCOPE=tests/<file>.spec.ts ENV=test-<slug>
UI: make test-ui SCOPE=tests/<file>.spec.ts ENV=test-<slug>
E2E: make test-e2e E2E_SPEC=tests/<file>.spec.ts API_PORT=… UI_PORT=… MAILDEV_UI_PORT=… ENV=e2e-<slug>

Full gates only at end of lot/branch: make test-api, make test-ui, make clean test-e2e.

Environment isolation (MANDATORY)

NEVER run test campaigns on ENV=dev — afterEach hooks purge real data.
Branch tests live in the isolated worktree on ENV=test-<slug> / ENV=e2e-<slug>; ENV is the LAST make argument.
NEVER add timeouts to make a flaky e2e pass — a timeout failure is a real bug (bad selector, race, regression). UI waits are <2s except AI generation.

AI-flaky allowlist (non-blocking)

CI is authority

CI was green on main → any branch failure IS a branch problem; never claim "pre-existing". Decide: evolution (adapt the test) or regression (fix the code). Local-green / CI-red → trust CI.