# Test Data Management

## Data Sources

| Source | Location | Type |
|--------|----------|------|
| Test coordinates | `_docs/00_problem/input_data/test_coordinates.md` | Static reference data |
| Expected results | `_docs/00_problem/input_data/expected_results/results_report.md` | Pass/fail criteria |
| Generated tiles | ./tiles/ (Docker volume) | Runtime artifacts |
| Output files | ./ready/ (Docker volume) | Runtime artifacts |

## Test Data Lifecycle

1. **Before test run**: Fresh PostgreSQL database (empty, migrations applied on API startup)
2. **During test run**: Each test creates its own data (unique GUIDs for routes/regions)
3. **After test run**: Data persists in volumes for inspection; DB data disposable

## Data Isolation

- Each test uses `Guid.NewGuid()` for region/route IDs — no conflicts between tests
- Tests run sequentially — no concurrency conflicts
- Tile cache is shared across tests (by design — tests tile reuse)

## Reference Coordinates

| Label | Latitude | Longitude | Use |
|-------|----------|-----------|-----|
| Tile/Region test point | 47.461747 | 37.647063 | Tile download, region processing |
| Route area (start) | 48.276067 | 37.384458 | Route creation, map processing |
| Route area (east) | 48.276067 | 37.519458 | Extended route (non-overlapping) |
