Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement retry strategy #1124

Open
testableapple opened this issue Jun 1, 2023 · 1 comment
Open

Implement retry strategy #1124

testableapple opened this issue Jun 1, 2023 · 1 comment
Labels
enhancement New feature request or improvement of an existing feature maestro cli Related to the command-line Maestro tool

Comments

@testableapple
Copy link

Is your feature request related to a problem? Please describe.
Most of the frameworks allow us to retry failed tests. Maestro currently does not. It would be great to have such an option.

Describe the solution you'd like

  • Maestro users can set up a retry-tests-count in the config file globally or in some flow in particular (similar to -retry-tests-on-failure flag in XCTest).
  • By default, this count should be equal to 0 (if flow fails, then it fails straight away)
  • If a user sets it up (e.g.: 3) and the flow fails on the first run, then Maestro automatically starts it from scratch, and so on
  • These repetitions are clearly displayed in the logs

Describe alternatives you've considered
N/A

Additional context
Reference: https://twitter.com/testableapple/status/1662915551927193609

@testableapple testableapple added the enhancement New feature request or improvement of an existing feature label Jun 1, 2023
@bartekpacia bartekpacia added the maestro cli Related to the command-line Maestro tool label Jul 26, 2024
@ubuntudroid
Copy link

This is an essential feature. As the Maestro Cloud docs correctly state:

The behavior of an application can be complex and challenging to verify, leading to unreliable test results in some instances. This can be caused by various factors such as animations, API calls, backend availability, network interruptions, and temporary outages.

We could for sure just restart the whole test suite ourselves if it fails, but that's far less efficient than just rerunning the failing tests. So a built-in mechanism similar to Maestro Cloud would be much appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature request or improvement of an existing feature maestro cli Related to the command-line Maestro tool
Projects
None yet
Development

No branches or pull requests

3 participants