Command reference
oko requirements coverage
How many of the operator's messages in each read session are indexed by Oko and accounted for by a session's reading, which session read each window, the windows still waiting, and the defect every correction, complaint, reported failure and repeated demand became.
Invocation#
oko requirements coverage [--session ID]... [--json]Inputs and options#
- --session ID (repeatable) names sessions, whole or by prefix; without it every read session is listed. A session no pass has read is not listed.
Output and state effect#
- Prints operatorMessages, indexed, indexedPercent, accounted, accountedPercent and sessions: per session its transcripts, operatorMessages, indexed, accounted, newestOperator (the index of his newest message), newestAccounted (the newest one a reading accounted for), unaccounted (message indices, those in waiting windows included), queued ({first, last, takenBy, refused}: a message waits when its index lies between first and last), readBy ({first, last, by}), corrections ({index, item, kind, requirement, defect}; kind is correction, complaint, failure or repeated) and coverage (accounted per hundred of his messages). Message indices are record positions in the transcript as Oko decodes it. Writes nothing.
Refusals and safe exits#
- Exits 0 with an empty sessions list for a session not read yet. A kept reading that cannot be read refuses naming its path (exit 1).