The answer

The verdict

A suite reported a pass with no failures and a total of 352, where the run before it had 374. Twenty-two checks were gone, the host had died partway through, and the only sign was a number nobody had a reason to read. Everything here follows from refusing that.

winwright run cases/report.wwx

winwright — cases/report.wwx

  preamble
    desk          this run's alone       nothing else is attached
    binary        bin/Debug/App.exe      built 2m ago, from the tree in hand
    staleness     current                sources unchanged since the build
    language      pt-BR                  settings.json -> ui.language
    foreground    granted                App — Relatorios
    spectators    none                   nothing else is showing this application
    display       not read               the application does not take Winwright.InApp

  assertions
    [held]  report.title.pt-BR          27 labels derived, 27 matched
    [held]  report.totals.rounding      derived from the app's own read-out
    [held]  store.unchanged             fingerprint equal, before and after
    [----]  capture.report              not observed — the shell would not open the
                                       overflow flyout, so the pane could not be
                                       brought to the front

Degraded (2). 3 assertions ran and held. 1 was never evaluated, and it is named above.

The member values are the exit codes

Not translated into them — a mapping written twice is a mapping that drifts, and CI reads the number rather than the word. 0 passed, 1 failed, 2 degraded, 3 broken. The last outranks the rest, because a reader told the build failed opens the wrong repository.

Three holes that are about the desk, not your application

✓A foreground Windows would not grant.
✓A focus that left the application while a menu walk or a traversal was polling.
✓A notification-area flyout the shell would not open.
✓None of them is your code being wrong, so none goes red — the answer names what the desk did instead.

One reading of the machine, before anything is asserted

The desk it is on, which binary it is driving, whether that binary is stale, the resolved language, the foreground, the launch arguments, whether anything else is showing the application, and whether the desk is this run's alone. Each is reported as measured, absent, or not read — an absent line and a missing line read the same to somebody skimming, and only one of them is a statement.

The roll call is part of the run

A run short of what discovery found is not reported as a pass. That is the original defect's own shape, so it is the one check that cannot be left to a convention.

Locators →