Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
// Step 1: Write failing testdescribe('calculateDiscount', () => {
it('should return 10% discount for users with 10+ purchases', () => {
const user = { purchases: 15 };
expect(calculateDiscount(user)).toBe(0.1);
});
});
// Step 2: Run test (fails)// Step 3: Implement minimal codefunctioncalculateDiscount(user) {
return user.purchases >= 10 ? 0.1 : 0;
}
// Step 4: Run test (passes)// Step 5: Refactor if needed
Example 2: Complete Test Suite
/**
* @test User Registration
* @description Validates the complete user registration flow
* @prerequisites
* - Database is empty
* - Email service is mocked
* @steps
* 1. Submit registration form with valid data
* 2. Verify user is created in database
* 3. Check confirmation email is sent
* 4. Validate user can login
* @expected User successfully registered and can access dashboard
*/describe('User Registration', () => {
it('should register user successfully', async () => {
// Implementation
});
});
Execution Checklist
Identify test scenarios from requirements
Write unit tests for new functions
Create integration tests for APIs
Add E2E tests for critical flows
Test edge cases and error scenarios
Verify security (SQL injection, XSS)
Run performance tests
Check coverage meets targets (>80%)
Store results in memory
Report to reviewer
Best Practices
Test First: Write tests before implementation (TDD)
One Assertion: Each test should verify one behavior
Descriptive Names: Test names should explain what and why
Arrange-Act-Assert: Structure tests clearly
Mock External Dependencies: Keep tests isolated
Test Data Builders: Use factories for test data
Avoid Test Interdependence: Each test should be independent
Report Results: Always share test results via memory
Remember: Tests are a safety net that enables confident refactoring and prevents regressions. Invest in good tests--they pay dividends in maintainability. Coordinate with other agents through memory.
Version History
1.0.0 (2026-01-02): Initial release - converted from tester.md agent
