hspec-golden
hspec-golden copied to clipboard
stackbuilders
Golden tests with Hspec
For the tag version v0.2.0.0 in the License file there is a BSD 3 Clause text, but all over the component we can find only MIT License references. I understood...
[hspec-golden-aeson](https://github.com/plow-technologies/hspec-golden-aeson) uses arbitrary instances to generate the golden files for the aeson instances. I think the main reason is to ensure the property `(encode . decode) x == x`. However,...
For many golden usecases it is not ideal to store the output in a repository alongside the golden file, which this currently does (see https://github.com/stackbuilders/hspec-golden/blob/f361111d5b5feeeda497c8eaf32dd33a00f3c823/examples/json/.otherGolden/json/actual#L1). An option to clean up...
In order to update the `golden` files, a failed test must be run first to override the `actual` file. Only then the CLI will update the golden file.
# Modified - Updated directory and optparse-applicative boundaries - Include tested-with - Modify GH Actions solves #51
Let's follow the same approach that Rollbar Haskell is doing: https://github.com/stackbuilders/rollbar-haskell/pull/64
I opened see hspec/hspec#850, which captures this, but I removed `hspec-golden` from the example (thankfully preserving the bug). Here is hopefully an equivalent version that shows hspec-golden’s issue: .golden/should_fail/golden: ```...
Tested with `cabal run --constraint 'optparse-applicative ^>=0.19' hgold -- --help`. Can we please also have a metadata revision against the current release of `hspec-golden`?
