The test-uv-tool CI job currently only smoke-tests the Robot Framework path (render→pabot→robot). PyATS tests require a real API endpoint and cannot be run in CI without a live device or a suitable mock.
Once a self-contained PyATS smoke test is feasible (e.g. via a mock testbed or sandbox environment), it should be added to the test-uv-tool job alongside the existing Robot smoke test to give full coverage of the uv tool install path.
The
test-uv-toolCI job currently only smoke-tests the Robot Framework path (render→pabot→robot). PyATS tests require a real API endpoint and cannot be run in CI without a live device or a suitable mock.Once a self-contained PyATS smoke test is feasible (e.g. via a mock testbed or sandbox environment), it should be added to the
test-uv-tooljob alongside the existing Robot smoke test to give full coverage of the uv tool install path.