[Feature Request] how to reduce delay between actions globally?

[DanteAndroid]

It seems that the delay is set to a very long value, which is about 1-2 seconds after ui is fully drawn. I would like to reduce the delay between actions globally, to get faster test speed in every flow.

[arildojr7]

Yeah, there are some waitForAppToSettle on code that make it slower. On a local build, I decreased its value and worked fine and faster. I'm sure it was introduced for some reason, but maybe there's another approach, like taking screenshots internally and comparing them (if the screenshoots are the same in a 300ms interval, we can assume that app is settle...)

[DanteAndroid]

Yeah, there are some waitForAppToSettle on code that make it slower. On a local build, I decreased its value and worked fine and faster. I'm sure it was introduced for some reason, but maybe there's another approach, like taking screenshots internally and comparing them (if the screenshoots are the same in a 300ms interval, we can assume that app is settle...)

If so I would like to know the reason. And your approach is inspiring!

[CyberCyclone]

The time between tests is a real pain point (5+ seconds!). The example video on the home page seems like it was artificially sped up. E.g, Tap events I want to be near instant and if I want to delay the next action, there's already assertVisible or assertNotVisible that can be used to delay actions. Once the conditions of those are met, then I want to immediately trigger the next action.

It would be nice to be able to configure this on a global setting if there's an action I want to deliberately wait, then there should be a waitTimeout as an action.

[ice-cap0]

yeah this would be great

[EvanPartidas]

Yeah, there are some waitForAppToSettle on code that make it slower. On a local build, I decreased its value and worked fine and faster. I'm sure it was introduced for some reason, but maybe there's another approach, like taking screenshots internally and comparing them (if the screenshoots are the same in a 300ms interval, we can assume that app is settle...)

Are you able to decrease total delay between tapOn commands to something along the lines of 100-250ms?

Even when setting waitToSettleTimeoutMs to a very low number I can't get the tapOn commands to be fast enough to beat a count-down timer in my app. This pitfall sadly makes maestro unusable for testing vital flows within my app. Not sure why it takes multiple seconds for Maestro to locate and tap on an element. Even this chimpanzee is way quicker than Maestro. Still a great tool, I really hope this delay thing gets fixed