feat(runtime): implement pilot runtime tap replay - #114
Merged
Merged
Conversation
Scenario capture YAML now accepts widgetTree instead of snapshot, default capture and failure diagnostics write widgetTree artifacts, and --print snapshot is rejected in favor of --print widget-tree. BREAKING CHANGE: capture.snapshot and --print snapshot are no longer accepted; use capture.widgetTree and --print widget-tree.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Pilot Runtime finder resolution and tap replay support, including structured failure handling and updated Scenario capture defaults.
What Changed
Why
This moves Flutter Pilot toward direct Pilot Runtime execution for Scenario interactions, reducing dependence on semantic-only matching and making tap failures explicit enough to debug.