[AZ-284] Autodev baseline + testability refactor

Phase A baseline outputs from /autodev (Steps 1-5):
- Problem & solution docs (_docs/00_problem, _docs/01_solution)
- Codebase documentation (_docs/02_document) incl. architecture,
  module-layout, glossary, system-flows, baseline compliance scan
- Test specs (blackbox, performance, resilience, security, resource,
  traceability matrix)
- Test task decomposition (_docs/02_tasks/todo): AZ-285..AZ-290
- Testability refactor (_docs/04_refactoring/01-testability-refactoring):
  - TC-01 Move DownloadedTileInfoV2 + new ExistingTileInfo to Common.DTO
  - TC-02 Replace dead ISatelliteDownloader API with real signatures
  - TC-03 GoogleMapsDownloaderV2 implements ISatelliteDownloader
  - TC-04 TileService depends on ISatelliteDownloader (mockable)
  - TC-05 DI + endpoints use ISatelliteDownloader
- Test runner scripts (scripts/run-tests.sh, run-performance-tests.sh)
- Autodev state pointer (_docs/_autodev_state.md)

Prepares the codebase for AZ-285..AZ-290 unit/integration test work.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-05-10 04:44:08 +03:00
parent 25a644a9bf
commit b0fffa6d42
68 changed files with 4192 additions and 11 deletions
@@ -0,0 +1,30 @@
# Unit Tests: RouteService
**Task**: AZ-288_route_service_tests
**Name**: Unit tests: RouteService (interpolation, geofence, distance)
**Complexity**: 3 points
**Dependencies**: AZ-285
**Component**: Blackbox Tests
**Tracker**: AZ-288
**Epic**: AZ-284
## Scenarios
- BT-06: Simple 2-point route — verify intermediate points at ≤200m spacing, point types correct
- BT-07: Route retrieval — verify GET returns same route with all points
- BT-10: Complex 10-point route — verify point distribution (1 first-original, 1 last-original, 8 intermediate)
- BT-11: Geofenced route — verify geofence region creation
- BT-12: Extended 20-point route — verify point distribution (1 first-original, 1 last-original, 18 intermediate)
- BT-N03: Route with <2 points — verify validation error
- BT-N04/N05: Invalid geofences — verify validation errors
## Test Data
Route points from test_coordinates.md (ROUTE-01 through ROUTE-06)
## Acceptance Criteria
AC-1: Point interpolation produces spacing ≤200m between all consecutive points
AC-2: Point type assignment is correct (original/intermediate)
AC-3: Total distance is calculated via Haversine
AC-4: Negative cases return appropriate errors