Skip to content

fix(maestro): repair existing Maestro flows - #1

Closed
EdgeClaws wants to merge 9 commits into
qa/maestro-graaljs-output-statefrom
qa/maestro-existing-test-fixes-clean
Closed

fix(maestro): repair existing Maestro flows#1
EdgeClaws wants to merge 9 commits into
qa/maestro-graaljs-output-statefrom
qa/maestro-existing-test-fixes-clean

Conversation

@EdgeClaws

Copy link
Copy Markdown
Owner

Stack

Depends on the isolated GraalJS state PR: EdgeApp#6171

This review branch contains only the existing-flow repairs, with one clean commit per affected test:

  • C000029a — tag correction
  • C000045 — token flow / shared import stabilization
  • C000034 — detected-token selection
  • C000046 — wallet rename
  • C000037 — split wallets
  • C000036 — Coreum autodetect
  • C000048 — current split-wallet title
  • C190284 — 2FA prompt
  • C999003 — logged-in Help flow

Deliberately excluded

  • C000035 disable
  • C184035 GRS/UFO coverage removal
  • C000048 Botanix expectation removal
  • unused Manage Tokens save-button test ID
  • net-zero launch workaround

Those are held out of this review rather than silently reducing coverage. C000045 retains its already-tracked temporary MOG assertion relaxation pending the linked product follow-up.

Verification

  • git diff --check
  • YAML parse of every changed Maestro flow/helper
  • no device run launched while reorganizing commits

After the Graal PR merges, this PR can be retargeted/rebased to EdgeApp/develop without carrying its diff.

@EdgeClaws

Copy link
Copy Markdown
Owner Author

Superseded by EdgeApp#6172, the single direct-to-develop Maestro repair PR.

@EdgeClaws EdgeClaws closed this Aug 21, 2026
@EdgeClaws
EdgeClaws deleted the qa/maestro-existing-test-fixes-clean branch August 21, 2026 22:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant