tasty-rerun alternatives and similar packages
Based on the "tasty" category.
Alternatively, view tasty-rerun alternatives based on common mentions on social networks and blogs.
tasty9.8 2.5 tasty-rerun VS tastyModern and extensible testing framework for Haskell
tasty-hedgehog8.6 6.3 tasty-rerun VS tasty-hedgehogTasty integration for the Hedgehog property testing library
tasty-discover8.3 0.0 tasty-rerun VS tasty-discoverTest discovery for the tasty framework.
tasty-golden8.2 0.0 tasty-rerun VS tasty-goldenGolden test support for Tasty
tasty-expected-failureMark test cases as expected-failure
tasty-hspec6.8 0.0 tasty-rerun VS tasty-hspecHspec provider for tasty
tasty-ant-xml6.6 1.2 tasty-rerun 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-xml6.0 0.0 tasty-rerun VS tasty-jenkins-xmlRender tasty output to XML for Jenkins in addition to other (console) output
tasty-html5.9 0.0 tasty-rerun VS tasty-htmlHTML test reporter for the Tasty test framework
tasty-th5.8 0.0 tasty-rerun VS tasty-thAutomatically generate tasty test groups from functions in a module using TH
tasty-silver5.5 3.0 tasty-rerun VS tasty-silverA fancy test runner for tasty and support for golden tests.
tasty-mgolden5.2 0.0 tasty-rerun VS tasty-mgoldenA different golden testing provider for tasty.
tasty-tmux4.5 0.0 tasty-rerun VS tasty-tmuxTerminal user acceptance testing via tmux
tasty-auto4.5 0.0 tasty-rerun VS tasty-autoDeprecated: Auto discovery for the Tasty test framework, use tasty-discover instead
tasty-leancheck4.0 0.0 tasty-rerun VS tasty-leancheckLeanCheck support for the Tasty test framework (Haskell)
tasty-stats4.0 0.0 tasty-rerun VS tasty-statsCollect statistics of your Tasty testsuite
tasty-laws4.0 0.0 tasty-rerun VS tasty-lawsTasty test runners for checking common laws
tasty-program3.3 0.0 tasty-rerun VS tasty-programUse tasty framework to test whether a program executes correctly
tasty-travis2.9 0.8 tasty-rerun VS tasty-travisFancy Travis CI output for tasty tests.
Static code analysis for 29 languages.
Do you think we are missing an alternative of tasty-rerun or a related project?
tasty testing framework
allows to filter a test tree depending
on an outcome of the previous run.
This may be useful in many scenarios,
especially when a test suite grows large.
- Rerun only tests, which failed during the last run (
--rerun). Combined with live reloading (e. g., using
stack test --file-watch), it gives an ultimate power to focus on broken parts and put them back in shape, enjoying a tight feedback loop.
- Rerun only tests, which have beed added since the last saved test run. This comes handy when writing a new module, which does not affect other parts of the system, or adding new test cases.
- Rerun only tests, which passed during the last saved test run. Sometimes a part of the test suite is consistently failing (e. g., an external service is temporarily down), but you want be sure that you are not breaking anything else in course of your work.
To add it to your test suite just replace
import Test.Tasty import Test.Tasty.Ingredients.Rerun main :: IO () main = defaultMainWithRerun tests tests :: TestTree tests = undefined
--help to list command-line options:
Rerun only tests, which failed during the last run.
If the last run was successful, execute a full test
suite afresh. A shortcut for
Update the log file to reflect latest test outcomes.
Read the log file and rerun only tests from a given
comma-separated list of categories:
successful. If this option is
omitted or the log file is missing, rerun everything.
If according to the log file and
is nothing left to rerun, run all tests. This comes
especially handy in
stack test --file-watch or
Location of the log file (default: