Electron desktop · actual MCP evidence · v0.5.0

From requirements to real Electron evidence

A linked journey through supplied requirements, the generated plan and cases, real execution results, screenshots and recorded application behavior.

26 / 26Typed suite cases passed
7 / 7Connection / native checks passed
504Screenshots captured · 484 published
4Manual cases explicitly not run

Follow the complete testing journey

Original acceptance started 2026-11-04T09:56:25.644Z · 108 seconds · 523 recorded steps · 0 healed

Recorded acceptance passed
01 / REQUIREMENTS

The supplied requirement sheet

Sixteen core requirements, connection acceptance, isolation rules and explicitly supplementary scope.

Read requirements →
02 / PLAN

The generated test plan

Mapped requirement IDs, acceptance criteria, scenarios, risks, constraints and open questions.

Explore the plan →
03 / CASES

Generated cases and expectations

Searchable cases with typed actions, observed locators, exact expectations and per-step evidence.

Browse test cases →
04 / EXECUTION

Actual acceptance results

26 typed suite cases and seven separately recorded connection/native checks. Healing remained off.

Open acceptance overview →
05 / DRILL-DOWN

Assertions, images and timings

Summary, detailed step report, raw evidence and requirement-to-case outcomes.

Inspect detailed results →
06 / COVERAGE

Coverage and known gaps

Recorded mappings and four unexecuted manual cases; a pass is scoped to the checks actually run.

Review requirement coverage →

Watch actual Electron execution

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.

Recording scope: these three cases completed successfully during a recording attempt that was later interrupted after video startup timeouts. This is not a video of all 26 cases. The complete supplied acceptance report above remains the authoritative 26/26 result.

Watch the requirements-to-report walkthrough

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.

Use the actual HTML report

Navigate the embedded report, open cases and expand assertions or screenshots.

Open full report ↗

Read the result in context

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.

Privacy and evidence integrity

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 →

Known coverage gaps

CaseNot executed / not claimedReason recorded in the acceptance plan
MAN01CSV download and selected-row CSV contentThe MCP 0.5.0 typed actions do not expose a browser download-event capture/save-path action. Native JSON export bytes were independently verified.
MAN02Physical task drag-and-drop gestureThe MCP 0.5.0 typed UI action schema has no drag action. The accessible keyboard alternative passed.
MAN03Audible playback and canvas pixel changesSUP03 verified the audio asset, canvas equivalent action, progress and meter. It did not assert audible output or compare pixels; no visual baseline was created.
MAN04Rich text bold and italic formattingSUP04 verified contenteditable input and submitted text. Character-range formatting was not exercised by the typed MCP suite.

Captured views of the published HTML

These browser previews show the published documents and report. They are separate from the 484 original application screenshots.