You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, setup suites already executed are tracked per fork, so a setup already run on the master will not prevent it from running again on a fork. While this is desired behavior in many cases, there are a lot of use cases for setup suites in which one would not like this behavior, but would rather want a "global setup suite tracking" behavior in which all forks and the master share the setup suite executed state.
This behavior should thus be customizable somehow, ideally in the scripts themselves, per setup suite, but maybe also by adding a switch to the test runner to change the behavior globally.
The text was updated successfully, but these errors were encountered:
Currently, setup suites already executed are tracked per fork, so a setup already run on the master will not prevent it from running again on a fork. While this is desired behavior in many cases, there are a lot of use cases for setup suites in which one would not like this behavior, but would rather want a "global setup suite tracking" behavior in which all forks and the master share the setup suite executed state.
This behavior should thus be customizable somehow, ideally in the scripts themselves, per setup suite, but maybe also by adding a switch to the test runner to change the behavior globally.
The text was updated successfully, but these errors were encountered: