oka_harness 0.9.1

Device E2E targets over oka's owning dev sessions (ADR-0026): launch an Android app via `oka dev`, pick the forwarded VM service URI up from the runner-session contract, and drive/assert it with the f [...]

Changelog

All notable changes to this package are documented here.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.9.1

See packages/oka/CHANGELOG.md for train-wide release notes.

0.8.1

• Part of the 0.8.1 train: usage-banner and doctor doc-pointer fixes in the oka CLI; no package-specific changes in this package.

0.8.0

• Widen universal_automation_interface to ^0.3.0 and resolve flutter_mcp_toolkit_core 7.0.1 (coordinate actions).

0.7.0

• Release train alignment with oka 0.7.0.

0.4.0

Added

• AndroidAppTarget (ADR-0026): an AppTarget over the owning oka dev session — builds/installs/launches through oka, reads the forwarded VM service URI from .flutter_mcp/runner-session.json (mcp_flutter ADR-0014 spec v2), streams adb logcat into the harness LogTap, and tears the owning session down on stop(). Refuses launch(build: false) — no second owner.
• driverForLiveSession(projectDir): attach a WidgetDriver to an already-running session without launching anything.
• Offline test suite: fake oka script covering launch → attach → stop, arg threading, and the no-session timeout/teardown path.