Test.Syd.Modify

Declare that all tests below must be run sequentially

Declare that all tests below may be run in parallel. (This is the default.)

Annotate a test group with Parallelism.

Declare that the order of execution of all tests below may be randomised.

Declare that the order of execution of all tests below must not be randomised.

Annotate a test group with ExecutionOrderRandomisation.

Modify the test timeout

Turn off timeouts

Turn off timeouts

Modify the number of retries to use in flakiness diagnostics.

Turn off retries

Make the number of retries this constant

Mark a test suite as "potentially flaky" with a given number of retries.

This will retry any test in the given test group up to the given number of tries, and pass a test if it passes once. The test output will show which tests were flaky.

WARNING: This is only a valid approach to dealing with test flakiness if it is true that tests never pass accidentally. In other words: tests using flaky must be guaranteed to fail every time if an error is introduced in the code, it should only be added to deal with accidental failures, never accidental passes.

Like flaky, but also shows the given message to the user whenever the test is flaky.

You could use it like this:

>>> flakyWith 3 "Something sometimes goes wrong with the database, see issue 6346" ourTestSuite

Mark a test suite as "must not be flaky".

This is useful to have a subgroup of a group marked as flaky that must not be flaky afteral.

Mark a test suite as 'potentially flaky', such that it will not fail if it is flaky but passes at least once.

Like potentiallyFlaky, but with a message.

Annotate a test group with FlakinessMode.

Mark a test suite as 'should pass'

Mark a test suite as 'should fail'

Annotate a test suite with ExpectationMode