InfiComponent Lab · acceptance execution report

Packaged Electron · InfiAutomation MCP 0.5.0 · fresh isolated run · 4 November 2026

Core acceptance16/16passed
All executed checks33/330 failed · 0 healed
Typed-suite steps523504 UI screenshots
Interactive follow-ups4not-run

Recorded result

All LAB01–LAB16 core acceptance cases passed. The fresh typed MCP run passed 26 of 26 cases, with 0 healed outcomes. Separate connection/native/configuration checks passed 7 of 7.

Core acceptance passed; exhaustive supplementary validation is incomplete. CSV byte-level exports, physical task dragging, audible playback/canvas pixels and rich-text range formatting remain explicitly not run.

Read test plan · Browse cases and evidence · Original MCP HTML report · Detailed step report · Requirement traceability

Application and actual runtime

ExecutableC:/InfiComponentLab\dist\win-unpacked\InfiComponentLab.exe
Executable SHA-25632e357fc856feadd1e51531f47811d2621483e5a58815eb4999154d7c9baea3b
MCP installationC:/InfiAutomation · 0.5.0
Owned Electron runtimeElectron 45.2.1 · Chromium 156.0.8078.75 · embedded Node 24.22.1 · Playwright 1.64.1
Run timestamp / duration2026-11-04T09:56:25.644Z · 107.91 seconds (typed MCP suite)
Suite ID2026-11-04T09-56-25-643Z-bb59180d
Data isolationC:/InfiComponentLab\.runtime\acceptance-execution-20261104-acceptance-rerun-1793786183771
PolicyHealing off; no baseline creation or approval; synthetic local data; http://127.0.0.1:49724, http://127.0.0.1:49725

Execution manifest · Observed runtime and native menu tree · All 21 observed page snapshots

Core requirement results

RequirementRequired behaviorExecuted casesOutcome
LAB01An owned packaged Electron launch opens the unique Workspace title and seven main navigation menu groups, each with three subpages.LAB01passed
LAB02Registration rejects missing required fields and saves a valid name, email and terms acceptance through the backend, displaying the submitted name.LAB02passed
LAB03Input controls expose observable values, including a keyboard-controlled slider, dates, multiple selection and a custom framework combobox.LAB03passed
LAB04Project validation enforces ABC-123 format, team size 1–20, an eight-character passphrase and matching confirmation.LAB04passed
LAB05Customers can be created, edited, searched and deleted through the renderer and persistent REST backend.LAB05, SUP06passed
LAB06The advanced grid supports five-row selection and pagination over the eighteen seeded records.LAB06passed
LAB07Native File > Export > Export JSON writes a JSON file and reports its path; native View > Compact mode toggles a real state.LAB07passed
LAB08An explicit DOM File menu saves a note, double click produces a result, and the disabled action stays disabled.LAB08passed
LAB09Submitting the workspace note dialog displays the entered value. Cancelling closes it without saving.LAB09passed
LAB10Tabs switch visible panels and expanding the project tree allows Reports to be selected.LAB10passed
LAB11A same-origin iframe form and an open shadow-root form save independent feedback values.LAB11passed
LAB12Wrong credentials are rejected; tester@example.test / LabPass!2026 signs in; session read and logout work.LAB12passed
LAB13A three-step order workflow validates input and confirmation and creates a persistent order.LAB13, SUP06passed
LAB14The intentional HTTP 503 scenario reports an error; switching to Success recovers; delayed content appears when ready.LAB14passed
LAB15Inspector opens in a separate uniquely titled renderer with an independently saved note, and selection can return to Workspace.LAB15passed
LAB16A customer created through the REST API appears as one matching row in the renderer.LAB16, SUP06passed

Supplementary and safety suite results

CaseExecuted scopeOutcome
SUP01Upload/download API returns identical bytes and renderer lists the real filepassed
SUP02Task keyboard alternative creates and moves a persistent taskpassed
SUP03Tooltip, popover, progress, meter and accessible canvas have observable resultspassed
SUP04Rich text value appears in valid project resultpassed
SUP05Preferences save real theme, compact mode, locale and notification valuespassed
SUP06A new owned launch reads persisted preferences, customer and orderpassed
SUP07Command search and activity filtering expose specific resultspassed
SUP08Slow request can cancel and then recover successfullypassed
SAFE01Test-mode reset requires confirmation, cancellation preserves data, confirmed reset restores seedpassed
SAFE02Without --test-mode, UI/native reset are unavailable and backend reset returns 403passed

Native export verification: passed · 6560 bytes · 18 customers. Actual exported JSON · File verification and hash.

Connection, native and configuration results

CaseExecuted scopeOutcome
CONN01Owned launch reports real runtime and native menu discoverypassed
CONN02CDP reports attached renderer-only capabilities and rejects native Menu APIpassed
CONN03CDP detach preserves app and current entered value on reconnectpassed
NATIVE01Explicit Windows UIA cancels an observed real OS message dialogpassed
NATIVE02Explicit Windows UIA cancels an observed real OS file pickerpassed
SAFE03Packaged configuration retains isolation, sandbox, web security and loopback bindingpassed
NATIVE03HTML file chooser uses observed UIA controls; upload persists and downloads identical bytespassed

Recorded outcomes · Expected CDP capability rejection · Packaged configuration audit

Observed Windows native message dialogObserved Windows native file picker

Native Electron menu invocation uses MenuItem.click. Windows UIA separately observes and operates real OS dialogs. Security settings are verified from the packaged configuration; no exploit-testing claim is made.

First-run failures and corrections

The first full suite recorded 24/26 passed cases. LAB08 encountered a renderer-startup/navigation readiness race; SUP07 used a label shared by the search button and input. The harness now waits for Workspace readiness and each native navigation destination, and uses the observed unique search input. No application code or assertions were weakened. A full rerun used a new profile and passed all 26 cases.

Preserved first-run HTML report · Original recorded failures · Preserved keyboard file-picker attempt.

The initial restricted-runner launch failed an Electron sandbox folder-access check; the desktop-capable execution context then launched the same packaged EXE with its sandbox enabled. The first supplementary upload attempt did not select a file through keyboard acceptance; its recorded outcome is retained. The follow-up used the observed native Open control and verified selected filename, persisted metadata and exact downloaded bytes.

Not-run follow-ups and practical limits

CaseScopeReasonOutcome
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.not-run
MAN02Physical task drag-and-drop gestureThe MCP 0.5.0 typed UI action schema has no drag action. The accessible keyboard alternative passed.not-run
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.not-run
MAN04Rich text bold and italic formattingSUP04 verified contenteditable input and submitted text. Character-range formatting was not exercised by the typed MCP suite.not-run

The full steps and expected results are saved in the case catalogue. These results concern the synthetic local application, not a production customer system or a mobile application.