write-unit-tests
Skill9 starsChanged 3 months agoMITView on GitHub
Write meaningful unit tests for target code
11 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- stripe/stripe-androidtheir own version, first seen Nov 5, 2026
- drewdoebereiner/write-unit-teststheir own version, first seen Oct 15, 2026
- Endava/BEEQtheir own version, first seen Oct 8, 2026
- CrowdDotDev/crowd.devtheir own version, first seen Oct 8, 2026
- razorpay/bladetheir own version, first seen Oct 8, 2026
- igorescodro/alkaatheir own version, first seen Oct 8, 2026
Used with
Projects with it also use write-e2e-tests.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
igorescodroSkillwrite-e2e-tests
Use when writing or modifying end-to-end tests in the Alkaa project — triggers on tasks like "add an E2E test", "write a flow test", "test this feature end-to-end", "add a test to shared module", or "cover this user journey with a test".
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- gologo13/agent-skills★ 087% same
Wrote their own version · 10
- tldraw/tldraw★ 51ksame name
- CrowdDotDev/crowd.dev★ 3.4ksame name
- igorescodro/alkaa★ 1.6ksame name
- stripe/stripe-android★ 1.6ksame name
- razorpay/blade★ 665same name
- Endava/BEEQ★ 162same name
- kennguyen887/agent-foundation★ 1same name
- cmnemoi/skills★ 0same name
- drewdoebereiner/write-unit-tests★ 0same name
- josecabralf/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- accessibility-auditSkill
- add-documentationSkill
- add-error-handlingSkill
- address-github-pr-commentsSkill
- agent-risk-reviewSkill
- agent-work-receiptSkill
- automation-roi-auditSkill
- blind-spot-passSkill
- code-reviewSkill
- commit-changes-mainSkill
- commit-same-branchSkill
- commitSkill
- create-pr-mainSkill
- debug-issueSkill
- decision-auditSkill
- define-agent-goalSkill
- design-agent-loopSkill
- fix-compile-errorsSkill
- fix-git-issuesSkill
- gauntlet-loopSkill
- generate-api-docsSkill
- generate-pr-descriptionSkill
- git-sync-workspaceSkill
- instruction-ablationSkill
- light-review-existing-diffsSkill
- lint-fixSkill
- lint-suiteSkill
- merge-open-prsSkill
- optimize-performanceSkill
- pathfinderSkill
- prompt-eval-debugSkill
- refactor-codeSkill
- requirement-to-implementationSkill
- run-all-tests-and-fixSkill
- scoped-auditSkill
- security-auditSkill
- seo-auditSkill
- setup-new-featureSkill
- structure-promptSkill
- tddSkill
- thermo-nuclear-code-quality-reviewSkill
- update-memory-bankSkill
- update-readmeSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 12 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's …
- Distinctive: line 13
Test all public methods and functions
- Distinctive: line 15
Test both positive and negative scenarios
- Distinctive: line 18
Use the project's testing framework conventions
- Distinctive: line 19
Write clear, descriptive test names
- Distinctive: line 20
Follow the Arrange-Act-Assert pattern
- Distinctive: line 29
Ensure tests are deterministic and repeatable
- Distinctive: line 30
Keep tests simple and focused on one thing
- Distinctive: line 31
Add helpful assertion messages
- Distinctive: line 49
Test observable behavior and public contracts, not implementation trivia.
- Distinctive: line 51
Do not commit, push, merge, or run destructive commands without explicit user consent.
- Distinctive: line 52
Do not print, log, or commit secrets or credentials found in the code or test fixtures.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's testing conventions.
Steps
- Test Coverage
- Test all public methods and functions
- Cover edge cases and error conditions
- Test both positive and negative scenarios
- Aim for high code coverage
- Test Structure
- Use the project's testing framework conventions
- Write clear, descriptive test names
- Follow the Arrange-Act-Assert pattern
- Group related tests logically
- Test Cases to Include
- Happy path scenarios
- Edge cases and boundary conditions
- Error handling and exception cases
- Mock external dependencies appropriately
- Test Quality
- Make tests independent and isolated
- Ensure tests are deterministic and repeatable
- Keep tests simple and focused on one thing
- Add helpful assertion messages
Write Unit Tests Checklist
- Tested all public methods and functions
- Covered edge cases and error conditions
- Tested both positive and negative scenarios
- Used the project's testing framework conventions
- Written clear, descriptive test names
- Followed the Arrange-Act-Assert pattern
- Included happy path scenarios
- Included edge cases and boundary conditions
- Mocked external dependencies appropriately
- Made tests independent and isolated
- Ensured tests are deterministic and repeatable
Guardrails
- Test observable behavior and public contracts, not implementation trivia.
- Mock only external boundaries (network, clock, filesystem); use real objects for the rest.
- Do not commit, push, merge, or run destructive commands without explicit user consent.
- Do not print, log, or commit secrets or credentials found in the code or test fixtures; flag any exposure instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.