Summary
The kobiton/automate plugin's bundled AGENTS.md (plugin v1.9.0, the version we evaluated) enumerates the session types:
"every session has a type: AUTOMATION (script- or agent-driven Appium), CLI (the bundled CLI wrapper), MANUAL (a human driving the portal live view). If a human opens the live view and interacts while an automation session runs, the session becomes MIXED"
So the documented set is AUTOMATION / CLI / MANUAL / MIXED.
getSession on a completed instrumentation run returned:
which is on none of those lists. The session was otherwise fully populated — test_report_url, log_url and video_url all present — so this was a normal, complete session, not a degenerate one.
Anything filtering or branching on session type from the documented enumeration silently drops instrumentation runs.
Ask
Correct the enumeration, and check it against the values the API can actually emit rather than against the values it was expected to emit. Same species as the framework-argument and deviceName-filter issues: the product states a confident wrong thing rather than failing.
Summary
The
kobiton/automateplugin's bundledAGENTS.md(plugin v1.9.0, the version we evaluated) enumerates the session types:So the documented set is
AUTOMATION/CLI/MANUAL/MIXED.getSessionon a completed instrumentation run returned:which is on none of those lists. The session was otherwise fully populated —
test_report_url,log_urlandvideo_urlall present — so this was a normal, complete session, not a degenerate one.Anything filtering or branching on session type from the documented enumeration silently drops instrumentation runs.
Ask
Correct the enumeration, and check it against the values the API can actually emit rather than against the values it was expected to emit. Same species as the framework-argument and
deviceName-filter issues: the product states a confident wrong thing rather than failing.