Closed mdadighat closed 2 months ago
Coverage Report
File Stmts Miss Cover Missing src/api config.py 29 11 62% 39–46, 70–81 satchecker.py 1 1 0% 1 src/api/adapters/repositories satellite_repository.py 54 4 93% 29, 33, 37, 41 tle_repository.py 80 5 94% 66, 72, 81, 90, 94 src/api/domain/models tle.py 19 1 95% 52 src/api/entrypoints extensions.py 10 1 90% 32 src/api/entrypoints/v1/routes routes.py 37 10 73% 22, 63, 92, 114–126 tools_routes.py 49 6 88% 49–51, 86–88 src/api/services validation_service.py 112 12 89% 139, 159, 162–169, 172–179, 260–261 src/api/services/tasks development_tasks.py 23 23 0% 1–145 ephemeris_tasks.py 40 14 65% 54–72, 115, 119, 146, 167–170 src/api/utils coordinate_systems.py 136 50 63% 34–45, 69–84, 104–108, 132–140, 160–172, 195–209, 235–256, 296–300, 409–413, 459 propagation_strategies.py 65 1 98% 123 TOTAL 937 139 85%
Tests | Skipped | Failures | Errors | Time |
---|---|---|---|---|
80 | 0 :zzz: | 0 :x: | 0 :fire: | 16.954s :stopwatch: |
Description:
Updated JSON results for the tools/get-tle-data endpoint to include the data_source for each TLE
Context:
Right now you can’t tell the difference between which TLEs came from Celestrak and which ones came from Space-Track - this is an issue because satellites can have different names in each source, so the TLE history can look confusing if the names switch back and forth (MESAT1 and OBJECT G for example.)
Jira issue: SCK-74