Skip to content

test(e2e): read the target errors from the action shots - #13

Merged
koji-1009 merged 1 commit into
mainfrom
test/fold-action-errors
Sep 23, 2026
Merged

koji-1009 merged 1 commit into
mainfrom
test/fold-action-errors

Conversation

@koji-1009

Copy link
Copy Markdown
Owner

The actions test took the --press text:Save shot twice: once in the loop, and again only to read the error of State / two buttons.
It also took a --tap text:Cancel shot for the "no widget matches" error, which the --hover and --focus shots of type:ElevatedButton already produce for State / two buttons; the harness finds every action's target through the same _target.

Each action shot in the loop now checks the error of State / two buttons, and the two extra shots (two flutter test runs) are gone.

🤖 Generated with Claude Code

The press shot was taken twice: once in the loop, and again to read the
two-buttons error. The tap on text:Cancel took one more shot for the
no-match error, which the hover and focus shots already produce: every
action finds its target the same way.

Each action shot now checks the two-buttons error, and the two extra
shots are gone.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@koji-1009
koji-1009 merged commit 4f40259 into main Sep 23, 2026
5 checks passed
@koji-1009
koji-1009 deleted the test/fold-action-errors branch September 23, 2026 05:31
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.

2 participants