testing-policy

Sterne1

Forks1

Aktualisiert4. März 2026 um 17:29

Deterministic, CI-ready quality verification with no regressions and no coverage drop.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

giulio-leone

giulio-leone/wpdash

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	Testing Policy
description	Deterministic, CI-ready quality verification with no regressions and no coverage drop.

Testing Policy Skill

Purpose

Guarantee deterministic, CI-ready quality verification with no regressions and no coverage drop.

Use when

Implementing or modifying any feature/fix
Preparing issue closure or PR merge

Required Test Layers

Unit tests (business logic/utilities/pure functions)
Integration tests (APIs/DB/cross-module flows, when applicable)
E2E tests (user-facing/critical flows, when applicable)
Non-regression checks (previously passing tests must remain green)

Procedure

Before changes: run full suite and record baseline (totals + line/branch coverage).
Implement changes and add/update tests.
After changes: rerun full suite and produce diff (added/removed/broken tests + coverage delta).
If any previously passing test breaks or coverage drops, fix before completion.
Ensure tests are deterministic, isolated, non-interactive, and CI-compatible.

E2E Notes

Cover happy path + key edge/error cases for each critical flow.
Prefer stable selectors (data-testid) over fragile CSS/DOM coupling.

Done Criteria

Full suite green, no regressions, coverage >= baseline.

Anti-patterns

Manual-only validation
Flaky timeout-driven E2E
Merging with coverage regression

Mehr aus diesem Repository

gleiches Repository

breaking-change-decision

giulio-leone/wpdash

Structured decision process between Non-Breaking and Breaking paths without relaxing quality gates.

2026-03-041

universal-completion-gate

giulio-leone/wpdash

Mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over.

2026-03-041

e2e-testing

giulio-leone/wpdash

Deterministic, CI-ready end-to-end validation for critical user flows.

2026-03-041

github-sync

giulio-leone/wpdash

Keep local plan and GitHub project artifacts perfectly aligned with milestones, issues, labels, and statuses.

2026-03-041

interaction-loop

giulio-leone/wpdash

Iterative decision loop with consistent user checkpoints and explicit stop criteria.

2026-03-041

planning-and-tracking

giulio-leone/wpdash

Execution plan with milestone/issue hierarchy, explicit dependencies, and safe parallelism.

2026-03-041

name	Testing Policy
description	Deterministic, CI-ready quality verification with no regressions and no coverage drop.

Testing Policy Skill

Purpose

Guarantee deterministic, CI-ready quality verification with no regressions and no coverage drop.

Use when

Implementing or modifying any feature/fix
Preparing issue closure or PR merge

Required Test Layers

Unit tests (business logic/utilities/pure functions)
Integration tests (APIs/DB/cross-module flows, when applicable)
E2E tests (user-facing/critical flows, when applicable)
Non-regression checks (previously passing tests must remain green)

Procedure

Before changes: run full suite and record baseline (totals + line/branch coverage).
Implement changes and add/update tests.
After changes: rerun full suite and produce diff (added/removed/broken tests + coverage delta).
If any previously passing test breaks or coverage drops, fix before completion.
Ensure tests are deterministic, isolated, non-interactive, and CI-compatible.

E2E Notes

Cover happy path + key edge/error cases for each critical flow.
Prefer stable selectors (data-testid) over fragile CSS/DOM coupling.

Done Criteria

Full suite green, no regressions, coverage >= baseline.

Anti-patterns

Manual-only validation
Flaky timeout-driven E2E
Merging with coverage regression