Hackage :: [Package]

tasty-golden: Golden tests support for tasty

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain] [Publish]

Warnings:

This package provides support for «golden testing». A golden test is an IO action that writes its result to a file. To pass the test, this output file should be identical to the corresponding «golden» file, which contains the correct result for the test. To get started with golden testing and this library, see Introduction to golden testing.

[Skip to Readme]

Properties

Versions 2.0, 2.0.1, 2.1, 2.2, 2.2.0.1, 2.2.0.2, 2.2.1, 2.2.1.1, 2.2.1.2, 2.2.2, 2.2.2.1, 2.2.2.2, 2.2.2.3, 2.2.2.4, 2.3, 2.3.0.1, 2.3.0.2, 2.3.1, 2.3.1.1, 2.3.1.2, 2.3.1.3, 2.3.2, 2.3.2.1, 2.3.3, 2.3.3.1, 2.3.3.2, 2.3.3.3, 2.3.4, 2.3.5, 2.3.6
Change log CHANGELOG.md
Dependencies base (>=4.9 && <5), bytestring (>=0.9.2.1), containers, deepseq, directory, filepath, optparse-applicative (>=0.3.1), tasty (>=1.3), tasty-golden, temporary, text, typed-process [details]
License MIT
Author Roman Cheplyaka
Maintainer Roman Cheplyaka <roma@ro-che.info>
Category Testing
Home page https://github.com/UnkindPartition/tasty-golden
Bug tracker https://github.com/UnkindPartition/tasty-golden/issues
Source repo head: git clone https://github.com/UnkindPartition/tasty-golden.git
Uploaded by AndreasAbel at 2025-12-15T08:59:19Z

Modules

[Index] [Quick Jump]

Flags

Manual Flags

NameDescriptionDefault
build-exampleDisabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Readme for tasty-golden-2.3.6

[back to package description]

This package provides support for «golden testing».

A golden test is an IO action that writes its result to a file. To pass the test, this output file should be identical to the corresponding «golden» file, which contains the correct result for the test.

To get started with golden testing and this library, see Introduction to golden testing.

Command-line options

To see the command-line options, run your test suite with --help. Here's an example output:

Mmm... tasty test suite

Usage: test [-p|--pattern PATTERN] [-t|--timeout DURATION] [-l|--list-tests]
            [-j|--num-threads NUMBER] [-q|--quiet] [--hide-successes]
            [--color never|always|auto] [--ansi-tricks ARG] [--accept]
            [--no-create] [--size-cutoff n]
            [--delete-output never|onpass|always]

Available options:
  -h,--help                Show this help text
  -p,--pattern PATTERN     Select only tests which satisfy a pattern or awk
                           expression
  -t,--timeout DURATION    Timeout for individual tests (suffixes: ms,s,m,h;
                           default: s)
  -l,--list-tests          Do not run the tests; just print their names
  -j,--num-threads NUMBER  Number of threads to use for tests
                           execution (default: # of cores/capabilities)
  -q,--quiet               Do not produce any output; indicate success only by
                           the exit code
  --hide-successes         Do not print tests that passed successfully
  --color never|always|auto
                           When to use colored output (default: auto)
  --ansi-tricks ARG        Enable various ANSI terminal tricks. Can be set to
                           'true' or 'false'. (default: true)
  --accept                 Accept current results of golden tests
  --no-create              Error when golden file does not exist
  --size-cutoff n          hide golden test output if it's larger than n
                           bytes (default: 1000)
  --delete-output never|onpass|always
                           If there is a golden file, when to delete output
                           files (default: never)

See also tasty's README.

Maintainers

Roman Cheplyaka is the primary maintainer.

Oliver Charles is the backup maintainer. Please get in touch with him if the primary maintainer cannot be reached.