./devel/hs-tasty-rerun, Rerun only tests which failed in a previous test run

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 1.1.19nb2, Package name: hs-tasty-rerun-1.1.19nb2, Maintainer: pkgsrc-users

This Ingredient for 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.

For example, tasty-rerun allows:

* Rerun only tests, which failed during the last run (--rerun). Combined
with live reloading (e. g., using ghcid or 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.

Master sites:

Filesize: 6.452 KB

Version history: (Expand)

CVS history: (Expand)


   2023-11-02 07:37:49 by Masatake Daimon | Files touched by this commit (1141) 
Log message:
Revbump all Haskell after updating lang/ghc96
   2023-10-31 18:55:54 by Masatake Daimon | Files touched by this commit (5) 
Log message:
devel/hs-tasty-rerun: import hs-tasty-rerun-1.1.19

This Ingredient for 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.

For example, tasty-rerun allows:

* Rerun only tests, which failed during the last run (--rerun). Combined
  with live reloading (e. g., using ghcid or 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.