Trouble running widget tests w/ 2 IDEA instances running
See original GitHub issueI used to be able to right-click on the code of a flutter test and select “Run <test name>” from the context menu. Recently, this started producing the following error in the UI instead of running the test:
2:23 PM Error running 'Semantics tree is populated mid-scroll': @NotNull method io/flutter/run/test/TestLaunchState.startProcess must not return null
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Why do some Flutter widget tests fail if executed together but ...
The solution was to wrap each test with tester.runAsync() testWidgets('widget test 2', (WidgetTester tester) async { await tester.
Read more >Graphical integration of running tests in plugin
Hello,I am able to run tests in the language for which I'm making a plugin. Currently I extend the CommandLineState class and implement......
Read more >Widget Testing With Flutter - FlutterDevs
In this article, we explore Widget Testing With Flutter. We will implement a demo of widget testing for our Flutter application, and why...
Read more >A Deep Dive Into Widget Testing in Flutter: Part II (Finder and ...
The WidgetTester allows us to interact with the test environment. Widget tests don't exactly run how they would run on a device since...
Read more >Testing Flutter Apps - Making Sure Your Code ... - YouTube
In this episode of the Boring Show, Filip and guest Anthony go over how to test your Flutter apps before publishing it and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We should track this down, that interaction is really not expected.
@pq, do you mind taking a look?