test-driven-development
Drive Safer Development With Tests
Teams need reliable ways to implement changes and fix bugs without relying on intuition or fragile manual checks. This skill guides a red-green-refactor workflow with repository-aware commands, focused tests, and full-suite verification.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "test-driven-development" from https://skillstore.io/skills/addyosmani-test-driven-development.md and its manifest at https://skillstore.io/api/skills/addyosmani-test-driven-development/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « test-driven-development ». A task completion bug leaves the completion timestamp empty.
RĂ©sultat attendu:
- Reproduction test: complete a task and assert that its status changes and its completion timestamp is present.
- Expected first result: the test fails because the timestamp is missing.
- Next step: implement the smallest fix, rerun the focused test, then run the full suite.
Utilisation de « test-driven-development ». A developer wants to test a list operation that sorts records.
RĂ©sultat attendu:
- Prefer an assertion on the returned order and values.
- Avoid asserting that a specific internal database query string was called.
- This keeps the test focused on observable behavior during refactoring.
Utilisation de « test-driven-development ». A browser change alters a critical checkout flow.
RĂ©sultat attendu:
- Run the focused automated tests first.
- Reproduce the flow in a browser and inspect console errors, network responses, DOM structure, styles, and a screenshot.
- Run the repository's full test suite after the change.
Audit de sécurité
SûrAll 44 static findings are false positives. The detections are Markdown backticks, code fences, testing guidance, headings, or a documentation link rather than executable shell code, path traversal, or reconnaissance. No prompt injection, data exfiltration, or other net-new intent-level finding was identified.
Facteurs de risque
âïž Commandes externes (37)
đ AccĂšs au systĂšme de fichiers (1)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/addyosmani-test-driven-development/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/addyosmani-test-driven-development?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/addyosmani-test-driven-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-test-driven-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/addyosmani-test-driven-development.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
addyosmani. (2026). test-driven-development security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-test-driven-development/audits/1Citation BibTeX
@techreport{addyosmani-addyosmani-test-driven-development-2026,
author = {addyosmani},
title = {test-driven-development security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/addyosmani-test-driven-development/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "test-driven-development security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-test-driven-development/audits/1"
identifiers:
- type: other
value: "skillstore:addyosmani-test-driven-development:audit:1"
description: "Skillstore immutable audit report identifier"
Comparer les variantes
10 variantes installablesChaque auteur reste un skill installable distinct. La variante recommandée est classée selon les preuves Skillstore.
Pourquoi cette variante est premiĂšre
dmjgilbert-test-driven-development
2026-09-09
obra-test-driven-development
2026-09-09
cycleaddict-test-driven-development
2026-09-09
cygnusfear-test-driven-development
2026-09-09
addyosmani-test-driven-development
2026-09-22
dyai2025-test-driven-development
2026-09-09
codingcossack-test-driven-development
2026-09-09
zhanlincui-test-driven-development
2026-09-09
sickn33-test-driven-development
2026-09-09
davila7-test-driven-development
2026-09-09
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Build New Features
Plan a failing test, implement the smallest passing behavior, and refactor while preserving verified outcomes.
Fix Reported Bugs
Turn a bug report into a reproduction test, confirm the failure, implement a fix, and check for regressions.
Verify Browser Changes
Combine automated tests with browser inspection of the DOM, console, network behavior, styles, and screenshots.
Essayez ces prompts
Guide me through writing a failing test for this behavior: [describe behavior]. Ask only for the repository test command and relevant file context.
Apply the Prove-It Pattern to this bug: [bug report]. Define the expected behavior, propose a reproduction test, and explain what failure would confirm the bug.
Review these tests for state-based assertions, isolation, determinism, meaningful names, and appropriate use of mocks. Suggest focused improvements without changing the intended behavior: [tests].
Create a verification plan for this change: [change]. Identify focused tests, integration or end-to-end coverage, browser checks when relevant, the repository's full-suite command, and risks that need manual review.
Bonnes pratiques
- Discover the repository's actual test command before starting the TDD cycle.
- Test observable behavior with deterministic, isolated cases.
- Run focused tests during iteration and the full suite after implementation.
Ăviter
- Writing implementation code before creating a test that demonstrates the expected behavior.
- Testing internal call sequences when an observable result can verify the behavior.
- Skipping tests or repeating unchanged test commands without a code change.
Foire aux questions
When should I use this skill?
What does red-green-refactor mean?
Does this skill choose the test command?
Should every test use mocks?
Does it support browser testing?
Can it replace a security review?
Détails du développeur
Auteur
addyosmaniLicence
MIT
RĂ©vision Skillstore
r1
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
RĂ©f
5d5054f8a23586f9b500fece1cb613a9dffc787b
RĂ©cence de maintenance
19/09/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ SKILL.md