tasty-discover 4.2.0 → 4.2.1
raw patch · 4 files changed
+37/−25 lines, 4 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- CHANGELOG.md +5/−0
- README.md +24/−14
- tasty-discover.cabal +6/−7
- test/DiscoverTest.hs +2/−4
CHANGELOG.md view
@@ -8,6 +8,11 @@ [Keep a Changelog]: http://keepachangelog.com/ [Semantic Versioning]: http://semver.org/ +# 4.2.1 [2018-06-06]++## Changed+- Migrated source code hosting to https://git.coop/lwm/tasty-discover.+ # 4.2.0 [2018-03-03] ## Fixed
README.md view
@@ -20,13 +20,13 @@ - [Maintenance](#maintenance) - [Acknowledgements](#acknowledgements) -Haskell auto-magic test discovery and runner for the [tasty framework].+Haskell auto-magic test discovery and runner for the [tasty test framework]. -[tasty framework]: https://github.com/feuerbach/tasty+[tasty test framework]: https://github.com/feuerbach/tasty Prefix your test case names and `tasty-discover` will discover, collect and run-them. All popular Haksell test libraries are covered. Configure once and then-just write your tests. Avoid forgetting to add test modules to your Cabal/Hpack+them. All popular Haskell test libraries are covered. Configure once 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. @@ -34,7 +34,7 @@ # Getting Started -There's 4 simple steps:+There are 4 simple steps: 1. [Create a test driver file in the test directory](#create-test-driver-file) 2. [Mark the driver file as the `main-is` in the test suite](#configure-cabal-or-hpack-test-suite)@@ -46,8 +46,8 @@ ## Create Test Driver File You can name this file anything you want but it must contain the correct-preprocessor definition for tasty-discover to run and also, to detect the-configuration. It should be in the top level of the test directory.+preprocessor definition for `tasty-discover` to run and to detect the+configuration. It should be at the top level of the test directory. For example (in `test/Driver.hs`): @@ -58,8 +58,8 @@ ## Configure Cabal or Hpack 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 the driver 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@@ -83,7 +83,7 @@ # Write Tests -Create test modules and correctly prefix the tests with the name that+Create test modules and prefix the test function name with an identifier that corresponds to the testing library you wish to run the test with: - **prop_**: [QuickCheck](http://hackage.haskell.org/package/tasty-quickcheck) properties.@@ -93,7 +93,7 @@ - **spec_**: [Hspec](http://hackage.haskell.org/package/tasty-hspec) specifications. - **test_**: [Tasty](http://hackage.haskell.org/package/tasty) TestTrees. -Here's an example test module:+Here is an example test module with a bunch of different tests: ``` haskell {-# LANGUAGE ScopedTypeVariables #-}@@ -144,7 +144,7 @@ # Customise Discovery -You configure tasty-discover by passing options to the test driver file.+You configure `tasty-discover` by passing options to the test driver file. ## No Arguments @@ -162,8 +162,10 @@ - **--generated-module**: The name of the generated test module. - **--ingredient**: Tasty ingredients to add to your test runner. -It is also possible to override tasty arguments with `-optF`:+It is also possible to override [tasty test options] with `-optF`: +[tasty test options]: https://github.com/feuerbach/tasty#options+ ``` bash {-# OPTIONS_GHC -F -pgmF tasty-discover -optF --hide-successes #-} ```@@ -186,7 +188,7 @@ # Deprecation Policy If a breaking change is implemented, you'll see a major version increase, an-entry in the [change log] and a compile time error with a deprecation warning+entry in the [change log] and a compile-time error with a deprecation warning and clear instructions on how to upgrade. Please do complain if we're doing this too much. @@ -201,6 +203,14 @@ # Maintenance If you're interested in helping maintain this package, please let [@lwm] know!++It doesn't take much time (max ~3 hours a month) and all we need to do is:++ * Triage issues that are raised.+ * Review pull requests from contributors.+ * Fix bugs when present.+ * Make releases.+ * Manage bounds issues on Stackage. You can [create an issue] or drop him a line at **lukewm AT riseup DOT NET**.
tasty-discover.cabal view
@@ -1,18 +1,18 @@--- This file has been generated from package.yaml by hpack version 0.20.0.+-- This file has been generated from package.yaml by hpack version 0.28.2. -- -- see: https://github.com/sol/hpack ----- hash: 7f57cc7ff691dc37cb2fc91f183182a851042dbf6e5e06d4c7e5250f1891f46c+-- hash: c69bb3382cc20b5891546bfbf1fc899a6933c635332b6a4d5bde683aee75193a name: tasty-discover-version: 4.2.0+version: 4.2.1 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. category: Testing stability: Experimental-homepage: https://github.com/lwm/tasty-discover#readme-bug-reports: https://github.com/lwm/tasty-discover/issues+homepage: http://git.coop/lwm/tasty-discover+bug-reports: http://git.coop/lwm/tasty-discover/issues author: Luke Murphy maintainer: Luke Murphy <lukewm@riseup.net> copyright: 2016 Luke Murphy@@ -20,14 +20,13 @@ license-file: LICENSE build-type: Simple cabal-version: >= 1.10- extra-source-files: CHANGELOG.md README.md source-repository head type: git- location: https://github.com/lwm/tasty-discover+ location: http://git.coop/lwm/tasty-discover library hs-source-dirs:
test/DiscoverTest.hs view
@@ -37,13 +37,11 @@ test_generateTree :: IO TestTree test_generateTree = do- input <- pure "Some input"+ let input = "Some input" pure $ testCase input $ pure () test_generateTrees :: IO [TestTree]-test_generateTrees = do- inputs <- pure ["First input", "Second input"]- pure $ map (\s -> testCase s $ pure ()) inputs+test_generateTrees = map (\ s -> testCase s $ pure ()) <$> pure ["First input", "Second input"] {-# ANN hprop_reverse "HLint: ignore Avoid reverse" #-} hprop_reverse :: H.Property