diff options
| author | blasty <peter@haxx.in> | 2026-07-24 14:24:05 +0200 |
|---|---|---|
| committer | blasty <peter@haxx.in> | 2026-07-24 14:24:05 +0200 |
| commit | 2a64e78edca6cacc13af17375e1c3d9de51b5ce8 (patch) | |
| tree | d57c5319b05c0f2e32988addf0bf971201e923dc /idatui/app.py | |
| parent | worker: inject custom tools on startup (self-sufficient, no spawn.sh needed) (diff) | |
| download | ida-tui-2a64e78edca6cacc13af17375e1c3d9de51b5ce8.tar.gz ida-tui-2a64e78edca6cacc13af17375e1c3d9de51b5ce8.tar.xz ida-tui-2a64e78edca6cacc13af17375e1c3d9de51b5ce8.zip | |
tests: add --worker <binary> to run the pilot suite against the idalib worker
run()/main() gain a worker path: IdaTui(open_path=binary, backend="worker",
ensure_server=False) instead of attaching to an mcp supervisor via --db. boot()
and every scenario are backend-agnostic (they drive app.program), so the full
31-scenario suite runs unchanged on the worker. This is the verification gate
before deleting the mcp transport:
~/ida-venv/bin/python tests/test_scenarios.py --worker targets/echo
The default (no --worker) still uses the mcp supervisor + --db, so nothing
regresses until we pull the plug.
Diffstat (limited to 'idatui/app.py')
0 files changed, 0 insertions, 0 deletions