Possible Flare bug in hit-test / sizing about developer_quest HOT 6 CLOSED

I've done a few quick tests to see if I could find something interesting.

I don't think it's related to size/hit test as even adding a driver.waitFor(_startGameFinder); before the tap call seems to hang up the driver. I also added a GestureDetector (just in case/to test) around the StartScreenHero to print out when it gets tapped on, but that never happens.

That made me wonder if the presence of the idle animation (basically painting every frame) is somehow holding the driver up, so I removed the animation by having the StartScreenHeroRenderObject always return false here:

@override
  bool get isPlaying => false;

This makes it paint the first frame, but not repaint.

That immediately worked/let it continue. It seems like the way we advance animations in Flare is somehow hanging up the driver (it works with the regular testing framework). Does the driver client wait for all painting to settle before propagating data/communicating back? It seems like something of the sort is happening.

from developer_quest.

Aha!
https://docs.flutter.io/flutter/flutter_driver/FlutterDriver/runUnsynchronized.html

By default, Flutter Driver waits until there is no pending frame scheduled in the app under test before executing an action. This mechanism is called "frame sync". It greatly reduces flakiness because Flutter Driver will not execute an action while the app under test is undergoing a transition.

from developer_quest.

This works!

  await driver.runUnsynchronized<void>(() {
	  return driver.tap(_startGameFinder);
  });

from developer_quest.

I had to make some other changes to make this work in the themed_tasks branch. Here's the commit:

https://github.com/luigi-rosso/dev_rpg/commit/20d9375350106fb0880b1459bbc19639b8a345f9

from developer_quest.

from developer_quest.

Thanks again! I'm closing this.

from developer_quest.