InfiAutomation MCP / Windows desktop example

Requirements and acceptance criteria

Seven mapped items, with their source, scope and open questions.

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.
UI01

Provisional: Standard mode exposes a visible result display and Clear resets it to zero.

Source: Observed Header, CalculatorResults and clearButton; acceptance expectation proposed from control semantics.

Cases: CALC01

Recorded coverage and outcomes →
UI02

Provisional: basic arithmetic produces mathematically correct integer results.

Source: Observed plusButton, minusButton, multiplyButton, divideButton and equalButton.

Cases: CALC02, CALC03, CALC04, CALC05

Recorded coverage and outcomes →
UI03

Provisional: Backspace removes the final entered digit.

Source: Observed number pad and backSpaceButton.

Cases: CALC06

Recorded coverage and outcomes →
UI04

Provisional: Square and Square root perform the named operations.

Source: Observed xpower2Button and squareRootButton.

Cases: CALC07, CALC08

Recorded coverage and outcomes →
UI05

Provisional: memory store, recall and clear function as named.

Source: Observed memButton, MemRecall and ClearMemoryButton.

Cases: CALC09

Recorded coverage and outcomes →
WF01

Use observed selectors, executable cases and explicit assertions; keep healing off for the first run.

Source: User request

Cases: CALC01, CALC02, CALC03, CALC04, CALC05, CALC06, CALC07, CALC08, CALC09

Recorded coverage and outcomes →
WF02

Close inspection session before execution, poll to completion and provide summary, detailed and requirement-coverage reports.

Source: User request

Cases: CALC01

Recorded coverage and outcomes →

Questions for the product owner

Requirement text · Continue to the plan →