refactor: move slow performance tests to extra test suite
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
This commit is contained in:
parent
fce01ddf83
commit
67e06e12ce
10 changed files with 433 additions and 5 deletions
|
|
@ -1654,6 +1654,28 @@ end
|
|||
- Mock external services
|
||||
- Use fixtures efficiently
|
||||
|
||||
**Performance Tests:**
|
||||
|
||||
Performance tests that explicitly validate performance characteristics should be tagged with `@tag :slow` or `@moduletag :slow` to exclude them from standard test runs. This improves developer feedback loops while maintaining comprehensive coverage.
|
||||
|
||||
**When to Tag as `:slow`:**
|
||||
|
||||
- Tests that explicitly measure execution time or validate performance characteristics
|
||||
- Tests that use large datasets (e.g., 50+ records) to test scalability
|
||||
- Tests that validate query optimization (N+1 prevention, index usage)
|
||||
|
||||
**Running Tests:**
|
||||
|
||||
```bash
|
||||
# Fast tests only (default)
|
||||
mix test --exclude slow
|
||||
|
||||
# Performance tests only
|
||||
mix test --only slow
|
||||
|
||||
# All tests
|
||||
mix test
|
||||
```
|
||||
---
|
||||
|
||||
## 5. Security Guidelines
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue