The supplied requirement sheet
Sixteen core requirements, connection acceptance, isolation rules and explicitly supplementary scope.
Read requirements →A linked journey through supplied requirements, the generated plan and cases, real execution results, screenshots and recorded application behavior.
Original acceptance started 2026-11-04T09:56:25.644Z · 108 seconds · 523 recorded steps · 0 healed
Sixteen core requirements, connection acceptance, isolation rules and explicitly supplementary scope.
Read requirements →Mapped requirement IDs, acceptance criteria, scenarios, risks, constraints and open questions.
Explore the plan →Searchable cases with typed actions, observed locators, exact expectations and per-step evidence.
Browse test cases →26 typed suite cases and seven separately recorded connection/native checks. Healing remained off.
Open acceptance overview →Summary, detailed step report, raw evidence and requirement-to-case outcomes.
Inspect detailed results →Recorded mappings and four unexecuted manual cases; a pass is scoped to the checks actually run.
Review requirement coverage →This is real renderer footage of three completed passing cases: navigation, registration validation/backend submission, and input controls. It was captured separately from the supplied full acceptance run.
154 seconds · 1380 × 900 · silent renderer capture · natural source playback speed. Native OS menu/dialog presentation is not recorded.
A real browser recording opens the requirement sheet, generated plan and case search, then drills into the actual MCP execution and requirement coverage. It ends at the execution-video player.
Navigate the embedded report, open cases and expand assertions or screenshots.
The first acceptance attempt recorded 24/26 passed and two failures. The supplied rerun recorded 26/26 passed, with healing off. History is retained rather than overwritten.
The seven connection/native checks are reported separately from the 26 typed cases. Requirement mapping does not prove exhaustive product coverage.
484 original renderer screenshots are published without pixel changes. Twenty captures showing machine runtime/export paths, and historical/OS captures containing private folder listings, are replaced with explicit privacy placeholders.
Machine paths in text artifacts use generic test-workspace paths. Original source hashes and published hashes are recorded. Assertions, outcomes and case IDs retain their recorded meaning.
Inspect publication provenance →| Case | Not executed / not claimed | Reason recorded in the acceptance plan |
|---|---|---|
| MAN01 | CSV download and selected-row CSV content | The MCP 0.5.0 typed actions do not expose a browser download-event capture/save-path action. Native JSON export bytes were independently verified. |
| MAN02 | Physical task drag-and-drop gesture | The MCP 0.5.0 typed UI action schema has no drag action. The accessible keyboard alternative passed. |
| MAN03 | Audible playback and canvas pixel changes | SUP03 verified the audio asset, canvas equivalent action, progress and meter. It did not assert audible output or compare pixels; no visual baseline was created. |
| MAN04 | Rich text bold and italic formatting | SUP04 verified contenteditable input and submitted text. Character-range formatting was not exercised by the typed MCP suite. |
These browser previews show the published documents and report. They are separate from the 484 original application screenshots.