3 runs (Jun 10 to Jun 12). Warnings count as passed; broken tests that never executed are excluded.
Run the following tests in order. Stop on the first failure.
tests/You are an autonomous AI testing agent that can interact with user interfaces through computer vision and input control. Your main responsibility is to execute test cases on a system to verify if the system works as expected.
Your task is to execute test cases to verify if the system you are operating is working as expected. Test cases are provided in a structured Markdown or CSV format. Some tests have a step with id "Precondition". This states a condition that must be met before you can start the execution!
Never expect credentials inside a test definition. When a step references credentials (e.g. "the QA credentials"), read them from the file referenced in the step or setup (conventionally secrets/credentials.txt) using your file tools at execution time.
You have a scratchpad to persist information from setup to test case executions or between different test case executions. Use the scratchpad_write_tool to append information and the scratchpad_read_tool to retrieve them. Only use the scratchpad when you are explicitly prompted to read from or write information to it!
Connect the tools around your QA process. Credentials stay in the OS secure store; per-project settings live in <project>/integrations.json.
Run summaries in a channel: pass/fail verdicts the team sees without opening the app.
A bot you chat with: /run a test from your phone, get the verdict back.
Import test cases into tests/testrail, publish run results back as a TestRail run.
Pick requirements, let AskUI inference draft executable test definitions from them.
Draft test definitions from Linear issues via AskUI inference.
Jira-native test management: import Xray tests, publish executions from local runs.
Profiles describe how to reach an agent-os controller. Connect from here, then drive them from Tests / Plans / LiveRun.
Profiles
Verifies that the driver can start turn-by-turn navigation from the Assistant card and that Google Maps renders an active route on the infotainment HMI. The agent tapped "Start navigation", confirmed Maps launched, and verified the route with live traffic and active guidance.
Google Maps launched from the Assistant card and the search bar appeared.
A route to the destination was drawn along US-101 with the green/red traffic overlay visible.
The current-position arrow follows the highlighted route and the ETA is shown.
Navigation session active; HMI on the Maps view.
The test PASSED. Navigation started from the Assistant and Google Maps rendered an active route with live traffic; guidance is following the current position.
36 message(s) from the running agent.