maestro icon indicating copy to clipboard operation
maestro copied to clipboard

Default timeout of commands should be documented in API reference

Open bartekpacia opened this issue 2 years ago • 4 comments

Commands that wait by default if the action cannot be performed immediately (e.g. tapOn on a view that is not yet visible, waitForAnimationToEnd) should have their timeouts clearly documented in API reference.

I just wanted to find out what the timeout for waitForAnimationToEnd is, and to do that, I had to look at the source code.

bartekpacia avatar Sep 21 '23 21:09 bartekpacia

Ah, it's here: https://maestro.mobile.dev/advanced/configuring-maestro-driver-timeout.

I think this page should be linked to from Commands.

bartekpacia avatar Sep 21 '23 21:09 bartekpacia

Ah, it's here: https://maestro.mobile.dev/advanced/configuring-maestro-driver-timeout.

MAESTRO_DRIVER_STARTUP_TIMEOUT is just for app startup. It doesn't change the default timeout between actions. E.g, an action that takes 60 seconds to process is terminated early even with MAESTRO_DRIVER_STARTUP_TIMEOUT set.

CyberCyclone avatar Mar 27 '24 05:03 CyberCyclone

Is there no way to actually configure command timeouts individually? I can't seem to find one 🤔

- runFlow:
    when:
      visible: "${INPUT_TEXT}.*" # I want to configure this to something like 1500ms
    commands:
      - tapOn: "${INPUT_TEXT}.*"

btrautmann avatar Aug 07 '24 18:08 btrautmann