Coding & Debugging
PromptBeginner5 minmarkdown
- **Missing assertions**: Tests that execute code but never assert on outcomes
giving false confidence.
0
Explore
Find agent skills by outcome
7,576 skills indexed with the new KISS metadata standard.
Showing 24 of 7,576Categories: Communication, Research & Learning, Cursor-rules, Coding & Debugging
Coding & Debugging
PromptBeginner5 minmarkdown
- **Hardcoded test data**: Using magic strings and numbers without factories
builders
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Over-mocking**: Mocking so many dependencies that the test validates the mocks
not the actual code.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- [ ] Test data is generated via factories or builders
not hardcoded.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Validate interactions across database
API
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Write test code following AAA pattern with clear arrange
act
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Implement** clean
maintainable test code following AAA pattern (Arrange
0
Coding & Debugging
PromptBeginner5 minmarkdown
Test Engineer Agent Role
# Test Engineer
0
Coding & Debugging
PromptBeginner5 minmarkdown
**RULE:** When using this prompt
you must create a file named `TODO_test-analyzer.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaand...
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Connects test data to business outcomes: user satisfaction
developer productivity
0
Coding & Debugging
PromptBeginner5 minmarkdown
- [ ] Coverage gaps are prioritized by risk (code churn
complexity
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Impact**: Developer time
CI delays
0
Coding & Debugging
PromptBeginner5 minmarkdown
Write all proposed analysis findings and any code snippets to `TODO_test-analyzer.md` only. Do not create any other files. If specific files should be created or edited
include patch-style diffs or clearly labeled file blocks inside the TODO.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Weight coverage by code complexity and change frequency
not just raw percentages
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Distinguish between code bugs
test bugs
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Rank all findings by impact: developer time saved
risk reduced
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Prioritize coverage improvements by combining code churn
complexity
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Analyze coverage gaps** by identifying untested code paths
missing edge case tests
0
Coding & Debugging
PromptBeginner5 minmarkdown
**RULE:** When using this prompt
you must create a file named `TODO_quality-engineering.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,...
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Treat test infrastructure as a first-class engineering concern with versioning
review
0
Coding & Debugging
PromptBeginner5 minmarkdown
- [ ] Coverage references cite relevant code areas
services
0
Coding & Debugging
PromptBeginner5 minmarkdown
In `TODO_quality-engineering.md`
include:
0
Communication
PromptBeginner5 minmarkdown
- Ensure contract tests cover all inter-service communication
not just happy paths
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Design chaos engineering experiments: fault injection
failure scenarios
0