Simon Hengel

We can consider this a bug. Our current approach is roughly based on https://www.schoolofhaskell.com/user/snoyberg/general-haskell/exceptions/catching-all-exceptions, which doesn't propagate `StackOverflow`. @snoyberg's `safe-exceptions` does not have this problem.

I think the following could make a nice API for this feature... ```haskell tag :: String -> SpecWith a -> SpecWith a tag = undefined ``` ...which then can be...

Only adding `--fail-on-focused` for now.

We now have `—strict` and `—fail-on=focused,pending,empty` + we have a PR for `--fail-on=empty-description` (#700 ). Closing.

Hey! Thanks for opening this issue and sorry for the late reply! Currently the `FailureReport` type is used for rerunning failed tests (see https://hspec.github.io/rerun.html). Let's look at that type: ```haskell...

@thomasjm Looking at again, I'm not comfortable with exposing `Test.Hspec.Core.FailureReport` in it's current form. What you can do as a workaround for now is defining ```haskell data FailureReport = FailureReport...

## Options I tried a couple of things, going forward I think there are technically 3 options: 1. Enable it by default for the `checks` formatter (and possibly others) 2....

@phadej Yes, it's possible to extend `hspec` by adding new instances for the `Example` type class. What currently is not possible, is adding new command-line options. So if you need...

@CristhianMotoche hey, I haven't worked on this. But I've been looking into allowing to add custom command line options. Not released yet, but this might come in handy for this...

[`hspec-golden`](https://hackage.haskell.org/package/hspec-golden) has been on Hackage for some time now. I haven’t had a chance to try it myself yet, but I am looking forward to. I’m going to close this...