Opentrons · Flex harness

flex-testing-agent

Release-driven robot test suggestions with live Jira and monorepo PR links.

← All suggestions

suggested · updated 2026-07-23

ODD Protocol Setup with loop and runtime parameters (Flex 9.1.2-alpha.1)

Touchscreen Protocol Setup smoke for AUTH-3041. Alpha.1 cherry-picked useMemo around protocol-modules and labware grouping so setup screens do not re-render excessively when a protocol uses loops and runtime parameters (RTP). This is the primary new test surface in v9.1.2-alpha.1 versus alpha.0.

Jira AUTH-3041 ODD re-render with loop and RTP during Protocol SetupPR #21946 fix(app) cherry picking for ODD rendering issue when using a loop with RTPPR #21905 fix(app): add useMemo to avoid unnecessary re-rendering for RTP
Monorepo branch chore_release-9.1.2
Compared tov9.1.2-alpha.0
Robot OS9.1.2-alpha.1
Hardware flex_touchscreen_odd, protocol_with_loop_and_rtp

Harness commands

uv run flex-test inspect
uv run flex-test probe --no-picture

Tests

IDPlan
E1
Confirm robot is on alpha.1
pass

ODD fix shipped in v9.1.2-alpha.1; confirm KansasFLEX is on that build before UI smoke.

  • Run `uv run flex-test inspect`.
  • Confirm installed software version is `v9.1.2-alpha.1` (or newer on the same branch).

KansasFLEX probe/inspect 2026-07-23: system/API/update-server v9.1.2-alpha.1; probe 43/43 acceptable
E2
Upload loop + RTP protocol
skipped

Repro path from AUTH-3041 / #21905 requires a protocol that uses a loop and runtime parameters.

  • Obtain the protocol attached to AUTH-3041 (or an equivalent protocol with at least one loop and one RTP).
  • Upload it to KansasFLEX (desktop app or robot Protocols screen).
  • Confirm analysis succeeds and the protocol appears on the robot.

Harness baseline done; needs AUTH-3041 protocol on ODD
E3
Protocol Setup remains responsive
skipped

#21946 and #21905 memoize protocolModulesInfo and labware setup groups so Protocol Setup Labware / Modules / deck screens do not thrash on RTP-driven updates.

  • On the Flex touchscreen, open the uploaded protocol and enter Protocol Setup.
  • Open Parameters (RTP) and change at least one runtime parameter value.
  • Navigate Labware setup and Modules and deck setup (and back).
  • Scroll lists if present; leave setup idle for several seconds.
  • Pass criteria: no freeze, blank flash, or runaway re-render; setup remains usable end-to-end.
  • Fail criteria: UI locks up, flickers continuously, or requires reboot to recover.

Operator touchscreen follow-up
E4
Complete setup readiness (optional)
skipped

Confirms setup can finish after RTP edits without a render-path failure.

  • With hardware matching the protocol (or as far as setup allows), proceed through Confirm.
  • Optional: start then cancel the run if motion is acceptable for this session.
  • Record whether Confirm / Run controls behaved normally after RTP changes.

Operator touchscreen follow-up