InfiAutomation MCP / Windows desktop example

Test plan

The original plan, scenarios and risks accompanying the recorded Calculator run.

Observed baseline, provisional expectations. No product requirement document was supplied. UI01–UI05 are UI-derived expectations. WF01–WF02 are workflow checks. The original plan and executable suite accompany the recorded report and 53 step screenshots.

Execution approach

  1. Review and approve the expectations; resolve missing business requirements.
  2. Open Calculator in Standard mode and inspect its live UI Automation tree.
  3. Review exact locators, requirement references and explicit assertions in the executable suite.
  4. Close inspection sessions, execute sequentially with healing off, and poll until completion.
  5. Inspect summary, individual steps, screenshots and mapped outcomes.

Readable plan (Markdown) · Saved plan (JSON) · Replay suite (JSON)

Nine planned scenarios

CaseScenarioRequirement referencesExpected assertions
CALC01Standard mode and resetUI01, WF01, WF02Standard mode visible; display zero.
CALC02AdditionUI02, WF012 + 3 = 5
CALC03SubtractionUI02, WF019 - 4 = 5
CALC04MultiplicationUI02, WF016 × 7 = 42
CALC05DivisionUI02, WF018 ÷ 2 = 4
CALC06BackspaceUI03, WF01Backspace removes last digit.
CALC07SquareUI04, WF01Square of 3 is 9.
CALC08Square rootUI04, WF01Square root of 9 is 3.
CALC09Memory lifecycleUI05, WF01Stored value recalled correctly and memory cleared.

Execution conditions and limits

Inspect executable cases →