Documentation

Run a bracket resource acquisition function around all the specs. The bracket opens before the first test case and closes after the last test case.

It works by actually spawning a new thread responsible for the resource acquisition, passing the resource along to the parent threads via a shared MVar. Then, there's a bit of logic to synchronize both threads and make sure that:

a) The 'Resource Owner' thread is terminated when the main thread is done with the resource.

b) The 'Main Thread' only exists when the resource owner has released the resource. Exiting the main thread before the 'Resource Owner' has released the resource could left a hanging resource open. This is particularly annoying when the resource is a running process!

Main Thread Resource Owner x | Spawn |----------------------->x | | | |-- Acquire resource | Send Resource | |<-----------------------| | | | | ... ... Await main thread signal | | | | | Send Signal | |----------------------->| | | | ... Release resource | Send Done | |<-----------------------| | Exit | Exit

A drop-in replacement for it that'll automatically retry a scenario once if it fails, to cope with potentially flaky tests.

It also has a timeout of 10 minutes.

Like it but with a custom timeout, which makes it realistic to test.

Mark a test pending because of flakiness, with given reason. Unless the RUN_FLAKY_TESTS environment variable is set.