You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing a semantic test (that is expected to fail), I see an unhelpful error. Previously, the error showed the diff of the expected properties and the actual ones, but I believe an exception is being thrown while calculating this diff.
Steps to Reproduce
Create a test using matchesSemantics or containsSemantics that is expected to fail
Run the test
Expected results: Test fails with error messaging that compares expected and actual output with no errors
Actual results: Test fails with error messaging containing errors
It looks like this issue was caused by changing the input to describeEnum in the matchers matches function from the SemanticAction to that SemanticAction's index as part of this PR.
It slipped through compile/analysis checks since the describeEnum method takes an Object, not something more specific. It looks like that non-specificity was needed to support flag (power of 2) enums, so not something we can make compile time safe at the moment.
I'll try to add in a test or two to prevent possible regressions while I'm in there fixing things.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Uh oh!
There was an error while loading. Please reload this page.
Originally reported @ b/243693776
When writing a semantic test (that is expected to fail), I see an unhelpful error. Previously, the error showed the diff of the expected properties and the actual ones, but I believe an exception is being thrown while calculating this diff.
Steps to Reproduce
matchesSemantics
orcontainsSemantics
that is expected to failExpected results: Test fails with error messaging that compares expected and actual output with no errors
Actual results: Test fails with error messaging containing errors
Code sample
Logs
The text was updated successfully, but these errors were encountered: