Scenario 1BUGSecurity & permissions
A signed‑out visitor can command drones
Approach
A fresh browser with no session follows the cockpit's own “Control panel” link and presses Take off; the simulator confirms the drone flew. Argus also reads the control API's CORS policy from a response header (read‑only).
Result
A visitor with no sign‑in took off a real drone, and the API trusts any origin. Maps to “let a signed‑out user open a page that should need sign‑in.”
no session · Drone 3 took off · Access‑Control‑Allow‑Origin: * · auth on flight commands: none
Scenario 2BUGTelemetry / freshness
A drone shown active while its data source is offline
Approach
Fly a drone; prove the cockpit updates live; then drop the feed, delay it 6 s, and take the simulator offline — comparing on‑screen distance, status and link badge with the simulator every 2 s.
Result
With the feed cut, the distance froze while the drone moved +105 m; with the simulator offline, the drone was still shown “in_flight” under a “connected” badge. Maps to “show a drone as online when it is offline.”
UI: connected · in_flight · 75 m · truth: simulator offline · +105 m · no stale indicator
Scenario 3BUGMap / visual
Drone and dock labels overlap on the map
Approach
Read the map's real label entities from the live Cesium viewer (text, screen position, font) and measure the overlap between label boxes.
Result
Each drone's status label overlaps its dock label and its altitude label — “560 m ASL” sits on top of “0 m” (100% overlap). The status text is unreadable at the default view.
Scenario 4BUGResponsive UI
On a phone, the video tile covers the 2D/3D map switch
Approach
Open the cockpit at 390×844 with touch; find the 2D button; check which element is actually on top at its centre; tap it with a real touch and verify whether the map mode changed.
Result
The 2D button's centre is covered by the video tile; a real tap lands on the video and the map mode never changes. Maps to “push the main action off screen at phone width.”
Scenario 5PASSResponsive UI · precision
Phone telemetry is reachable — no false alarm
Approach
Open the cockpit at phone width; locate every telemetry field by meaning; scroll each into its own scroll container; check whether it becomes visible and is not covered.
Result
Every field is reachable by scrolling the panel — PASS. Argus distinguishes “below the fold but reachable” from “truly unreachable,” avoiding a false positive.