2.1 KiB
2.1 KiB
Collision Prepare Flow Test Plan
Goal
Verify the deployed qaup-app service can complete the interface-only preparation flow for simulated collision objects before live position and alert testing.
Scope
This plan only verifies:
- Health endpoint is reachable.
- Simulated aircraft, unmanned vehicle, and special vehicle can be registered.
- Aircraft route query both returns route data and binds the route.
- Unmanned and special vehicle routes can be directly submitted and bound.
- Preparation status changes from
not readytoready.
This plan does not verify:
- Real position ingestion.
- Real collision point calculation from live tracks.
- WebSocket alert delivery.
- Real stop/recover signal dispatch.
Recommended Execution Location
Run inside the qaup-app container if possible, or on a host that can access the container port.
Examples:
docker exec -it qaup-app sh -lc 'bash /opt/qaup/deploy/test_collision_prepare_flow.sh'
BASE_URL="http://127.0.0.1:8080" bash deploy/test_collision_prepare_flow.sh
Script Inputs
The script supports environment variables:
BASE_URLHEALTH_PATHAIRCRAFT_IDUNMANNED_IDSPECIAL_IDAIRCRAFT_ROUTE_TYPEAIRCRAFT_IN_RUNWAYAIRCRAFT_OUT_RUNWAYAIRCRAFT_CONTACT_CROSSAIRCRAFT_SEATAIRCRAFT_START_SEATAUTH_HEADER
Default execution assumes no authentication because the current platform HTTP integration document states these endpoints are unauthenticated.
Expected Result
The script should end with:
PASS: collision preparation interface flow is ready for deployment testing
The preparation status before binding should report missing routes.
The preparation status after binding should report:
ready=trueregisteredCount=3missingRouteCount=0
Failure Handling
If the script fails:
- Confirm
qaup-appis healthy. - Confirm the service port matches
BASE_URL. - Confirm the aircraft route query parameters are valid in the target environment.
- If formal environment adds authentication later, set
AUTH_HEADER.