0/3 ready

Dashboard

3 runs (Jun 10 to Jun 12). Warnings count as passed; broken tests that never executed are excluded.

3Total runs
100%Avg pass rate
1Passed (latest)
0Failed (latest)
0Broken (latest)
0Warnings (all)
Test status over timepassedfailedbroken
Jun 10
Jun 11
Jun 12
Pass rate over time
Jun 10Jun 12
Latest run: Jun 12 19:32
navigate_to_destination PASSED
Open in Runs →
plans / smoke.md

Smoke Plan · Run on every change

Run the following tests in order. Stop on the first failure.

  • LOGIN_001 · valid login
  • All tests in tests/
prompts / system_capabilities.md

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.

  • You are utilizing a computer with internet access.
  • Your primary goal is to execute tasks efficiently and reliably while maintaining system stability.
  • You must interact with the system by taking screenshots and executing clicks or entering text.
  • Additionally, you can read or write files through dedicated tools that are available to you.
  • Operate independently and make informed decisions without requiring user input.
  • When using your function calls, they take a while to run and send back to you. Where possible/feasible, try to chain multiple of these calls all into one function calls request.
  • If you need to execute a click, make sure to move the mouse to the correct position first!

Test Case Format

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!

Credentials

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.

Scratchpad

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!

Custom agent tools (askui Tool subclasses) in helpers/
helpers / shell_command_tool.py
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
# Tool store: Shell / CLI. Wire an instance into cua_runner.py's act_tools. import subprocess from askui.models.shared.tools import Tool class ShellCommandTool(Tool): def __init__(self) -> None: super().__init__( name="run_shell_command", description=( "Run a shell command on the host machine and return its exit " "code and output. Use for CLI verification steps, e.g. " "checking a service status or reading a version number." ), input_schema={ "type": "object", "properties": { "command": { "type": "string", "description": "The command line to execute.", }, "timeout_seconds": { "type": "integer", "description": "Kill the command after this many seconds (default 30).", }, }, "required": ["command"], }, )

Integrations

Connect the tools around your QA process. Credentials stay in the OS secure store; per-project settings live in <project>/integrations.json.

SlackPosting

Run summaries in a channel: pass/fail verdicts the team sees without opening the app.

TelegramNot connected

A bot you chat with: /run a test from your phone, get the verdict back.

TestRailNot connected

Import test cases into tests/testrail, publish run results back as a TestRail run.

JiraNot connected

Pick requirements, let AskUI inference draft executable test definitions from them.

LinearNot connected

Draft test definitions from Linear issues via AskUI inference.

XrayNot connected

Jira-native test management: import Xray tests, publish executions from local runs.

Devices

Profiles describe how to reach an agent-os controller. Connect from here, then drive them from Tests / Plans / LiveRun.

No devices connected yet. Pick a profile below and click Connect.

Profiles

Local
This machine, agent-os contr…
localhost:23000 · display 1
Local Service
This machine, agent-os contr…
localhost:26000 · display 1
Test
chromium
Android devices ip:port
No Android devices detected. Plug one in via USB (with USB debugging enabled) or connect a wireless device above.
new_test.md
tests / new_test.md
1 2 3 4 5 6 7
# New test ## Steps 1. increase the temperature on the right seat by 2 Expect that temperature is at 65 on the right seat
navigate_to_destination PASS Open in Explorer

Summary

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.

Preconditions

  1. Vehicle in Park with the infotainment HMI on the home screen.
  2. Network available for map tiles and routing.

Test Steps

1. Tap "Start navigation" on the AssistantPASS

Google Maps launched from the Assistant card and the search bar appeared.

2. Verify the route renders with live trafficPASS

A route to the destination was drawn along US-101 with the green/red traffic overlay visible.

3. Confirm guidance is activePASS

The current-position arrow follows the highlighted route and the ETA is shown.

Postconditions

Navigation session active; HMI on the Maps view.

Conclusion

The test PASSED. Navigation started from the Assistant and Google Maps rendered an active route with live traffic; guidance is following the current position.

Live run

36 message(s) from the running agent.

Chat
Type a prompt and hit Run.
SurfaceDisconnected
Run on
Connect 'Local' on the Devices page firstOpen Devices
Default workspace
Conversation3 acts · 11 tool calls
1 Test · /Users/jonasmenesklou/Documents/testing/tests/navigate_to_destination.md Pass 3 calls
Open the Assistant, start navigation to "1600 Amphitheatre Pkwy", and verify Google Maps shows an active route.▾ show more
I'll tap "Start navigation" on the Assistant card, then take a screenshot to confirm Google Maps rendered the route with live traffic.512 → 47 · 340ms
click"Start navigation"→ ok
Take screenshotfull→ 1920×1080
Route is active on the map. [image]