Skip to main content
While Mo tests, it records each flow it exercises as a test case with its account, prerequisites, steps, and status. A session started with --no-test-cases, or one where Mo has not recorded a case yet, lists none.

cases list

Prints a JSON array of the session’s current cases, in the order Mo recorded them:
status is running, verified, issues_found, or blocked. statusReason is the filed bug or evidence for issues_found, the blocker for blocked, and null otherwise or when Mo recorded neither. account is empty when the case runs signed out. bugs lists filed bugs only, and each id works with qa bugs describe. Linked bugs may take a few more minutes to appear under a test case while they are verified.

cases describe

Prints one case with its prerequisites and the steps of one run, in order. Checks are steps too. <case> is the id or the exact name. An unknown case fails and lists the ids and names of up to 20 of the session’s cases.
evidence is what settled the status. It is null while the case is running or when Mo recorded none.

Options

string
Write the JSON to this file instead of stdout and print the file’s path.