Add optional timeout to tests?

[smassung]

Does it seem useful to have a timeout option on tests? For example, a third parameter to it:

it("should do something", [&](){
      AssertThat(something, IsTrue());
}, 10);

where this indicates a timeout of 10 seconds (or whatever). By default, there could be no timeout, or a user can set a default timeout via a command line parameter.

I'm imagining a use case where bandit is part of CI tests, and we don't want infinite looping tests.

[smassung]

(or should this be something that's handled at a higher level, such as in the CI tool, or in the command running the tests?)

[joakimkarlsson]

I think this would add complexity to bandit without enough gain to be warranted. My suggestion is to either handle this in your build system or in your tests.