List requirements without passed/no test

Every requirement without a passed test execution in one view (SR-120): no verification record with method test and result passed, of any version, holds there (spec question #532). Each with its verification status.

Command evidence.withoutPassedTest. Reads the workspace and changes no file.

Input

Field	Type	Required	Description
`view`	`view`	no	Default: the core. A variant: only records for it count, and only requirements its view holds (SR-047, SR-043).
`limit`	`integer`	no	Default: `200`.
`offset`	`integer`	no	Default: `0`.

Output

Field	Type	Required	Description
`elements`	array of `element`	yes	One page, by type, then identifier, else short ID: every requirement (type with the meaning `requirement`, status not marked invalid, applies in the view) without a verification record with method `test` and result `passed` that holds in the view, of any version and also when a later run failed (spec question #532). Each as evidence.status gives it, with `verification` and `validation`.
`total`	`integer`	yes	Every listed requirement, not only the page.
`view`	`viewId`	yes	core, or the variant of the view.
`incomplete`	`incomplete`	no	A repository of the workspace, or of an evidence location, is not on this machine: its requirements, or a passed test there, are not seen (SR-006 AK2).
`names`	array of `elementName`	no	The elements that `verification` names by UUID only, each once in the order first named: the variant of the view and the missing children (`missingChildren`), so a reader names them by short ID, identifier and title (#588). Left out when it names none.

App

In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command List requirements without passed/no test.

CLI

reqseq evidence without-passed-test, with --json for the output as JSON. Its help:

Usage: reqseq evidence without-passed-test [options]

Every requirement without a passed test execution in one view (SR-120): no
verification record with method test and result passed, of any version, holds
there (spec question #532). Each with its verification status.

Options:
  --view <value>          Default: the core. A variant: only records for it
                          count, and only requirements its view holds (SR-047,
                          SR-043).
  --limit <number>        default: 200
  --offset <number>       default: 0
  --input <json|@file|->  command input as JSON: inline, from a file, or from
                          standard input
  --workspace <path>      workspace root (default: nearest folder upwards with
                          reqseq-workspace.yaml)
  --json                  print exactly the command output as JSON
  --yaml                  print the whole command output as YAML, problems one
                          per line
  -h, --help              show help

API

POST /v1/commands/evidence.withoutPassedTest on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.

MCP

Tool evidence_withoutPassedTest of the MCP server (reqseq mcp), with the input as its arguments.