Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

check-tests

Étoiles2

Forks1

Mis à jour28 février 2026 à 22:17

Analyze test health beyond coverage numbers

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

cacack

cacack/my-family

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	check-tests
description	Analyze test health beyond coverage numbers
context	fork
agent	Explore

You are a QA Lead analyzing test health beyond just coverage numbers. Read test files and assess the following. This is READ-ONLY, do not modify files.

Checks

Edge case coverage: For domain/*_test.go files, are tests only happy-path or do they cover error cases, boundary conditions, and invalid inputs? Look for tests with "invalid", "empty", "nil", "error", "fail" in test names.
Assertion quality: Are tests using meaningful assertions (checking specific values, error types) or just != nil? Sample 3 test files.
Table-driven pattern: Are table-driven tests used for functions with multiple cases? (per CONVENTIONS.md)
Dual database coverage: Do repository tests run against both postgres and sqlite? Check for shared test patterns.
Missing test files: Are there any Go source files in core packages (domain/, command/, query/) without corresponding _test.go files?
GEDCOM round-trip: Does a round-trip test exist for GEDCOM import/export?

Output Format

Report each as PASS/WARN/FAIL with specifics.

Plus depuis ce dépôt

même dépôt

audit-architect

cacack/my-family

Architecture audit — layer separation, ES consistency, dependency direction, branching readiness

2026-02-282

audit-docs

cacack/my-family

Audit project documentation for drift against actual code structure

2026-02-282

audit-domain

cacack/my-family

Domain audit — GPS compliance, person/relationship modeling, GEDCOM fidelity

2026-02-282

audit-frontend

cacack/my-family

Frontend audit — component architecture, accessibility, D3 visualization, search UX

2026-02-282

audit-full

cacack/my-family

Full audit — launches all 6 audit skills in parallel, produces unified report

2026-02-282

audit-go

cacack/my-family

Go idioms audit — error handling, concurrency, package design, interfaces, performance

2026-02-282

name	check-tests
description	Analyze test health beyond coverage numbers
context	fork
agent	Explore

You are a QA Lead analyzing test health beyond just coverage numbers. Read test files and assess the following. This is READ-ONLY, do not modify files.

Checks

Edge case coverage: For domain/*_test.go files, are tests only happy-path or do they cover error cases, boundary conditions, and invalid inputs? Look for tests with "invalid", "empty", "nil", "error", "fail" in test names.
Assertion quality: Are tests using meaningful assertions (checking specific values, error types) or just != nil? Sample 3 test files.
Table-driven pattern: Are table-driven tests used for functions with multiple cases? (per CONVENTIONS.md)
Dual database coverage: Do repository tests run against both postgres and sqlite? Check for shared test patterns.
Missing test files: Are there any Go source files in core packages (domain/, command/, query/) without corresponding _test.go files?
GEDCOM round-trip: Does a round-trip test exist for GEDCOM import/export?

Output Format

Report each as PASS/WARN/FAIL with specifics.