Coding & Debugging
PromptBeginner5 minmarkdown
Write all proposed test plans
test code
0
Explore
Find agent skills by outcome
17,957 skills indexed with the new KISS metadata standard.
Showing 24 of 17,957Categories: Data, Openclaw, Productivity, Coding & Debugging, Creative
Coding & Debugging
PromptBeginner5 minmarkdown
- **Missing assertions**: Tests that execute code but never assert on outcomes
giving false confidence.
0
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
Data
PromptBeginner5 minmarkdown
- Log relevant context (input data
state) on failure for faster diagnosis.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- [ ] Test data is generated via factories or builders
not hardcoded.
0
Data
PromptBeginner5 minmarkdown
- Manage test data lifecycle to ensure isolated
repeatable scenarios.
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
Data
PromptBeginner5 minmarkdown
- Define test data requirements including fixtures
factories
0
Creative
PromptBeginner5 minmarkdown
- Design test matrix covering critical paths
edge cases
0
Data
PromptBeginner5 minmarkdown
- **Create** test data generators
factories
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Implement** clean
maintainable test code following AAA pattern (Arrange
0
Creative
PromptBeginner5 minmarkdown
- **Design** comprehensive test cases covering happy paths
edge cases
0
Productivity
PromptBeginner5 minmarkdown
- Assign each task a stable ID (e.g.
TASK-1.1) and use checklist items in outputs.
0
Productivity
PromptBeginner5 minmarkdown
- Treat every requirement below as an explicit
trackable task.
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
Test Engineer Agent Role
# Test Engineer
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Connects test data to business outcomes: user satisfaction
developer productivity
0
Data
PromptBeginner5 minmarkdown
- Transforms overwhelming data into clear
actionable stories that teams can act on
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Impact**: Developer time
CI delays
0
Coding & Debugging
PromptBeginner5 minmarkdown
- [ ] Coverage gaps are prioritized by risk (code churn
complexity
0
Data
PromptBeginner5 minmarkdown
- Summary of test data sources
analysis period
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