tasty-silver alternatives and similar packages
Based on the "tasty" category.
Alternatively, view tasty-silver alternatives based on common mentions on social networks and blogs.
-
tasty-hedgehog
Tasty integration for the Hedgehog property testing library -
tasty-expected-failure
Mark test cases as expected-failure -
tasty-rerun
Rerun previous test suite runs to run only failing tests -
tasty-test-reporter
An ingredient for tasty that prints a summary and outputs junit xml that works with jenkins. -
tasty-ant-xml
A tasty ingredient to output test results in XML, using the Ant schema. This XML can be consumed by the Jenkins continuous integration framework. -
tasty-th
Automatically generate tasty test groups from functions in a module using TH -
tasty-jenkins-xml
Render tasty output to XML for Jenkins in addition to other (console) output -
tasty-auto
Deprecated: Auto discovery for the Tasty test framework, use tasty-discover instead -
-
tasty-leancheck
LeanCheck support for the Tasty test framework (Haskell) -
tasty-program
Use tasty framework to test whether a program executes correctly
Access the most powerful time series database as a service
Do you think we are missing an alternative of tasty-silver or a related project?
|
Static code analysis for 29 languages.
sponsored
www.sonarqube.org
|
Popular Comparisons
-
tasty-silvervstasty-golden
-
tasty-silvervstasty-hspec
-
tasty-silvervstasty-rerun
-
tasty-silvervstasty-th
-
tasty-silvervstasty-ant-xml
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
Tasty Silver
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.
Interactive Mode
If the test runner is called with the -i option, the diff of any failing golden test is shown
to the user. Based upon this diff, the user can choose to update the golden standard or to
fix the test case as necessary. Interactive mode requires that at least git diff and less is
available, or preferrably wdiff and colordiff for character-based diffs.
Examples
For a non-trivial example see the Agda tests, which is used for testing the Agda compiler.
Maintainers
Philipp Hausmann is the primary maintainer.