Skip to content

Conversation

stevemessick
Copy link
Member

@pq

This is a hack. But the test runs. The failure had nothing to do with any test code we have control over. I think it is due to something that was added to the Kotlin test framework, but I don't know for sure.

@stevemessick
Copy link
Member Author

This also fixes FlutterSdkUtilTest.shouldInstallFlutterSDK()

@stevemessick stevemessick requested a review from pq April 19, 2019 21:53
@pq
Copy link
Collaborator

pq commented Apr 19, 2019

Neat! Is there any way we could make sure we're only ignoring the desired runtime exception? Or maybe that's not worth it?

@stevemessick
Copy link
Member Author

stevemessick commented Apr 19, 2019 via email

@pq
Copy link
Collaborator

pq commented Apr 19, 2019

Got it. If you think this might miss genuine failures, you could do something to check the class name but that's totally up to you. Thanks for following up!

Copy link
Collaborator

@pq pq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@stevemessick
Copy link
Member Author

Thanks for the tip. I'll do that in a follow-up PR.

@stevemessick stevemessick merged commit 0748be3 into master Apr 22, 2019
@stevemessick stevemessick deleted the main-test branch April 23, 2019 15:12
alexander-doroshko pushed a commit to alexander-doroshko/flutter-intellij that referenced this pull request Jan 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants