tasty-mgolden alternatives and similar packages
Based on the "tasty" category.
Alternatively, view tasty-mgolden alternatives based on common mentions on social networks and blogs.
tasty9.8 2.2 tasty-mgolden VS tastyModern and extensible testing framework for Haskell
tasty-hedgehog8.6 6.1 tasty-mgolden VS tasty-hedgehogTasty integration for the Hedgehog property testing library
tasty-discover8.3 0.0 tasty-mgolden VS tasty-discoverTest discovery for the tasty framework.
tasty-golden8.2 0.0 tasty-mgolden VS tasty-goldenGolden test support for Tasty
tasty-rerun7.4 1.7 tasty-mgolden VS tasty-rerunRerun previous test suite runs to run only failing tests
tasty-expected-failureMark test cases as expected-failure
tasty-hspec6.9 0.0 tasty-mgolden VS tasty-hspecHspec provider for tasty
tasty-ant-xml6.6 1.2 tasty-mgolden VS tasty-ant-xmlA tasty ingredient to output test results in XML, using the Ant schema. This XML can be consumed by the Jenkins continuous integration framework.
tasty-test-reporterAn ingredient for tasty that prints a summary and outputs junit xml that works with jenkins.
tasty-jenkins-xmlRender tasty output to XML for Jenkins in addition to other (console) output
tasty-html5.9 0.0 tasty-mgolden VS tasty-htmlHTML test reporter for the Tasty test framework
tasty-th5.8 0.0 tasty-mgolden VS tasty-thAutomatically generate tasty test groups from functions in a module using TH
tasty-silver5.5 3.2 tasty-mgolden VS tasty-silverA fancy test runner for tasty and support for golden tests.
tasty-auto4.5 0.0 tasty-mgolden VS tasty-autoDeprecated: Auto discovery for the Tasty test framework, use tasty-discover instead
tasty-tmux4.5 0.0 tasty-mgolden VS tasty-tmuxTerminal user acceptance testing via tmux
tasty-laws4.0 0.0 tasty-mgolden VS tasty-lawsTasty test runners for checking common laws
tasty-leancheck4.0 0.0 tasty-mgolden VS tasty-leancheckLeanCheck support for the Tasty test framework (Haskell)
tasty-stats4.0 0.0 tasty-mgolden VS tasty-statsCollect statistics of your Tasty testsuite
tasty-program3.3 0.0 tasty-mgolden VS tasty-programUse tasty framework to test whether a program executes correctly
tasty-travis2.9 0.8 tasty-mgolden VS tasty-travisFancy Travis CI output for tasty tests.
Access the most powerful time series database as a service
Do you think we are missing an alternative of tasty-mgolden or a related project?
Text based golden tests for tasty, with multi line (colored) diff expectation failure reporting.
Basically this package can turn any
IO Text action into a golden test via providing a
This package is the small brother of tasty-golden which also implements the same golden testing pattern.
tasty-mgolden is less generic and more opinionated than its bigger brother.
But for that reason can also offer more ergonomic defaults for its core use case:
Golden testing for
IO Text actions. Where:
- The text value is assuemd to contain multiple lines.
- The expectation failures can be rendered nicely in multi line diffs.
- The diff lines are colored via the tasty infrastructure
- The diff rendering is not done via the external
diffcommand, but uses the
Expectation diffs are rendered like developers are used to:
- Removed lines rendered in red.
- Added lines in green.
This is taken from the [example](example) directory in the repository.
To run these execute from repository root:
stack build stack exec tasty-mgolden-example
Contents of [example/example-a.txt](example/example-a.txt)
Contents of [example/example-b.txt](example/example-b.txt)
import Test.Tasty import Test.Tasty.MGolden main :: IO () main = defaultMain $ testGroup "golden tests" [ goldenTest "example-a" "example/example-a.txt" $ pure "foo\nbar\n" , goldenTest "example-b" "example/example-b.txt" $ pure "foo\nbaz\n" ]
golden tests example-a: OK example-b: FAIL foo -bar +baz 1 out of 2 tests failed (0.00s)
--update flag to accept the changes:
golden tests example-a: OK example-b: OK UPDATE All 2 tests passed (0.00s)
PRs on these are welcome.
- Improve the multi line diff reporting to only show a minimal context around the changed hunks.
- Add line markers in unified diff format.
- Change to
- Future? Upstream this to