The problem it solves

Automotive targets — Android head units, Linux/QNX ECUs, anything on adb, SSH or a COM port — live cabled to bench PCs that you reach over RDP. Testing them usually means brittle personal scripts, copy-pasted terminals, and screenshots pasted into spreadsheets.

TurboBench replaces that with one workflow:

 design in the browser  →  the RDP machine runs the test itself  →  report with evidence

• Manual engineers build tests from 100+ ready templates — no code.
• Python engineers drop in any CLI script and it becomes a drag-and-drop step.
• Everyone gets the same reports: expected vs actual per step, webcam photos/videos, screen recordings, DLT/logcat attachments, trends.

Highlights

Quick start

pip install turbobench     # pulls turboadb + turbossh automatically
tb                         # starts the server and opens the browser

First five minutes:

1. Configuration — add your RDP machine / SSH device / Android serial (auto-detected dropdowns, one Test button each).
2. Test Designer — drop in templates ("Check boot completed", "Webcam photo", "Run a script/.exe"), set expected results.
3. Run ▸ Run on: your RDP machine — the bench executes it and the Execution console streams every step live.
4. Reports — open the run: expected vs actual, evidence gallery, Allure, email, Xray.

Locked-down bench? Use the portable build

python scripts/build_pypi.py       # dist/turbobench-<ver>.whl (UI included)
python scripts/build_portable.py   # dist/turbobench-portable-win64.zip

Unzip on the bench, double-click TurboBench.cmd — Python is inside, no installation, no admin rights.

Your scripts, three ways

Action:  Run a script/.exe file (with args)     [system.run_file]
path:    C:/bench/power_control.py
args:    ["normal_power_cycle", "--port", "COM5"]

Every path supports cwd, env, timeout, retries, repeat, continue-on-fail, {{steps.N.output}} placeholders, and file-pattern assertions (match_file + match_pattern).

Two eyes on the target

• Webcam steps use the USB camera pointed at the display — proof of what physically showed.
• PC screen steps capture the bench PC's desktop (screenshot or recording); the RDP machine: desktop … steps do the same on a remote box.
• Live Feed streams either one, clearly labelled.

Architecture in 30 seconds

Browser (React) ── REST/WS ── FastAPI server ── SQLite ── artifacts/
     designer · recorder · scheduler · reports · vault · plugins
                        │
     "Run in RDP": test pushed over SSH (turbossh), executed natively
     by the bench PC (its adb via turboadb, its scripts, its devices),
     results + evidence pulled back automatically
                        │
   Android · Linux · QNX · serial · power rig · webcam — cabled to the bench

Exports keep you portable: every test case downloads as a standalone pytest file that runs anywhere with plain pytest.

Development

scripts/run-dev.ps1          # backend :8000 + Vite HMR frontend :5173
python -m pytest tests/      # unit suite

License

MIT © Naveen Daniel Kennedy — built on turboadb and turbossh.