30 lines
732 B
Markdown
30 lines
732 B
Markdown
# Testing Strategy
|
|
|
|
## Overview
|
|
|
|
CalMiner will use a combination of unit, integration, and end-to-end tests to ensure quality.
|
|
|
|
## Frameworks
|
|
|
|
- **Backend**: pytest for unit and integration tests.
|
|
- **Frontend**: (TBD) pytest with Selenium or Playwright.
|
|
- **Database**: pytest fixtures with psycopg2 for DB tests.
|
|
|
|
## Test Types
|
|
|
|
- **Unit Tests**: Test individual functions/modules.
|
|
- **Integration Tests**: Test API endpoints and DB interactions.
|
|
- **E2E Tests**: (Future) Playwright for full user flows.
|
|
|
|
## CI/CD
|
|
|
|
- Use GitHub Actions for CI.
|
|
- Run tests on pull requests.
|
|
- Code coverage target: 80% (using pytest-cov).
|
|
|
|
## Running Tests
|
|
|
|
- Unit: `pytest tests/unit/`
|
|
- Integration: `pytest tests/integration/`
|
|
- All: `pytest`
|