test-driven-development
Develop behavior through a failing test or reproducer, implementation, and refactoring. Use when test-first development is requested or a new behavior or bug fix benefits from an executable regression before implementation.
v2026.11.13-21cd5683 installazioni+3 in 7 giorni39 StelleMITsincronizzato 11 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/test-driven-developmentScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto976c39a7…2c3dd80f
976c39a7f848…0dc42c3dd80f1 file · 1.8 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/AeonDave/malskill/tree/main/coding-behaviours/test-driven-development@21cd568
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
Make the intended behavior observable before implementing it, then use the check to guide a small complete change. A passing test supports the behavior it covers; it is not a proof of correctness.
Choose the appropriate entry point
- For a new behavior or reproducible bug, use the failing-check loop below when practical. Follow explicit user and repository testing requirements.
- For a behavior-preserving refactor, establish a passing baseline and add characterization only for relevant uncovered behavior. Keep those checks green; do not manufacture a failure for behavior that should stay unchanged.
- For code already written, preserve it and assess the missing verification. Add meaningful checks; use an isolated pre-change baseline or controlled fault to test their sensitivity when useful. Do not discard work or restart implementation merely to recreate test-first history.
- For exploration, configuration, generated artifacts, or changes that do not benefit from a new automated test, choose the appropriate existing check, generator test, static validation, or reproducible manual procedure. State what remains unverified; do not describe tests written afterward as a test-first sequence.
For an urgent incident, use systematic-debugging to prioritize authorized mitigation and preserve evidence. Missing deterministic reproduction does not forbid investigation or recovery.
RED-GREEN-REFACTOR
- Specify one behavior and its observable outcome. Reuse a relevant existing check or failing artifact rather than creating a duplicate.
- RED: write the smallest useful test/reproducer and run it. Confirm that failure represents the missing behavior or defect; distinguish an intentionally absent API from an unrelated import, fixture, or environment error.
- GREEN: implement the smallest complete change that satisfies the behavior. Run the focused check and relevant neighboring cases; do not weaken assertions to make it pass.
- REFACTOR: improve the affected structure while preserving the contract and keeping checks green. Use
software-architecturefor consequential design or simplification decisions. - Continue and verify: take the next behavior when needed and run applicable broader checks. Use
verification-before-completionfor required gates, evidence freshness, and completion claims.
Diagnose an unexpected test result
- If a proposed regression already passes, check whether the behavior exists, the intended path ran, and the chosen input/assertion can detect the defect. A passing characterization test is expected.
- If setup fails, repair the relevant fixture or environment before treating the result as evidence about the behavior.
- If setup is excessive, inspect the test scope and existing seams before changing production APIs. Use
testing-reliabilityfor weak assertions, misleading doubles, fixture coupling, or flakes.
Apply to security tooling
For parsers, exploit harnesses, or payload tooling, preserve the relevant input, seed, transcript, or artifact before changing code and turn it into a bounded local regression where practical. Use testing-reliability for what the assertion must establish and the language/domain testing skill for harness mechanics.
Use software-guidelines for patch scope and affected consumers. Language-specific testing skills own framework syntax and execution commands.
File di questa versione
- SKILL.md3.8 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 nov 2026 | 21cd568 | 976c39a7 | Firmata | – |
Altro da AeonDave
Tutto da questo editoreAltro in Reverse engineering e fuzzing
Vai alla categoriaChiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login