packages feed

tasty-discover 4.1.2 → 4.1.3

raw patch · 3 files changed

+11/−12 lines, 3 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

CHANGELOG.md view
@@ -8,6 +8,13 @@ [Keep a Changelog]: http://keepachangelog.com/ [Semantic Versioning]: http://semver.org/ +# 4.1.3 [2018-01-01]++## Fixed+- Re-enable on Stackage due to tasty/tasty-hedgehog failure (see issue [#132]).++[#32]: https://github.com/lwm/tasty-discover/pull/132.+ # 4.1.2 [2017-12-19]  ## Fixed
README.md view
@@ -10,14 +10,6 @@  [tasty framework]: https://github.com/feuerbach/tasty -# Maintenance--If you're interested in helping maintain this package, please let @lwm know!--We're currently two people, @minad included, keeping an eye and trying to respond to issues.--I currently have less and less time that I can spare to work on this. Any help appreciated.- # Getting Started  There's 4 simple steps:@@ -44,8 +36,8 @@ ## Configure Cabal Test Suite  In order for Cabal/Stack to know where the tests are, you'll need to configure-the main-is option of your test-suite to point to that file. In the following-example, the test driver file is called Driver.hs:+the main-is option of your test-suite to point to the driver file. In the+following example, the test driver file is called Driver.hs:  ``` test-suite test
tasty-discover.cabal view
@@ -2,10 +2,10 @@ -- -- see: https://github.com/sol/hpack ----- hash: 38c30e2aaa0ce753221b60acaf08bd424fd91e93fdd8a22ba67f1eb52b9b8ee1+-- hash: 5e21264f08d3ea239d539e1a1ee915ebaee0edd7c09319014e9fad439b1f9f00  name:           tasty-discover-version:        4.1.2+version:        4.1.3 synopsis:       Test discovery for the tasty framework. description:    Automatic test discovery and runner for the tasty framework.                 Prefix your test case names and tasty-discover will discover, collect and run them. All popular test libraries are covered. Configure once and then just write your tests. Avoid forgetting to add test modules to your Cabal/Hpack files. Tasty ingredients are included along with various configuration options for different use cases. Please see the `README.md` below for how to get started.