project-testing
Custom test patterns and fixtures for {project}. Covers E2E, integration, and specialized testing requirements.
What this skill does
<!-- Generated by ai-dev-kit:recommend-skills on {date} -->
<!-- This skill can be safely deleted if no longer needed -->
# {project} Testing Patterns
Custom testing patterns, fixtures, and strategies for this project.
## Variables
| Variable | Default | Description |
|----------|---------|-------------|
| COVERAGE_TARGET | 80 | Minimum coverage percentage |
| E2E_TIMEOUT | 30000 | E2E test timeout in ms |
| PARALLEL_TESTS | true | Run tests in parallel when possible |
## Instructions
1. Identify test type needed (unit/integration/e2e)
2. Use appropriate fixtures and patterns
3. Follow project naming conventions
4. Ensure proper cleanup
## Red Flags - STOP and Reconsider
If you're about to:
- Write a test without proper isolation
- Skip cleanup in fixtures
- Hardcode test data instead of using fixtures
- Write flaky tests (timing-dependent, order-dependent)
**STOP** -> Use proper fixtures -> Ensure isolation -> Then write test
## Test Categories
### Unit Tests
Location: `tests/unit/`
Patterns:
- Test single functions/methods in isolation
- Mock external dependencies
- Fast execution (< 100ms each)
### Integration Tests
Location: `tests/integration/`
Patterns:
- Test component interactions
- Use test database/fixtures
- May have external dependencies
### E2E Tests
Location: `tests/e2e/` or `playwright/`
Patterns:
- Test full user workflows
- Use browser automation
- Longer execution time acceptable
## Fixtures
### Database Fixtures
Location: `tests/fixtures/`
Usage:
```python
# Python example
from tests.fixtures import sample_user, sample_order
def test_order_creation(sample_user, sample_order):
# Test uses pre-configured fixtures
pass
```
### Mock Services
Location: `tests/mocks/`
Available mocks:
- [TODO: List project-specific mocks]
## Naming Conventions
| Test Type | File Pattern | Function Pattern |
|-----------|-------------|------------------|
| Unit | `test_*.py` | `test_<function>_<scenario>` |
| Integration | `test_*_integration.py` | `test_<component>_<action>` |
| E2E | `*.spec.ts` | `test('<feature> - <scenario>')` |
## Coverage Requirements
| Component | Minimum Coverage |
|-----------|-----------------|
| Core logic | 90% |
| API routes | 80% |
| Utilities | 70% |
## CI Integration
Tests run in CI:
- On PR: unit + integration
- On merge: all including E2E
- Nightly: full regression suite
## Customization
Edit this file to add:
- New fixture definitions
- Additional mock services
- Custom test patterns
- Coverage exceptions
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.