tasty-discover 3.0.1 → 3.0.2
raw patch · 3 files changed
+13/−13 lines, 3 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- CHANGELOG.md +11/−2
- README.md +1/−10
- tasty-discover.cabal +1/−1
CHANGELOG.md view
@@ -8,9 +8,18 @@ [Keep a Changelog]: http://keepachangelog.com/ [Semantic Versioning]: http://semver.org/ -# 3.0.1 [2017-05-04]+# 3.0.2 [2017-06-05] ### Fixed+- Make upper bounds for dependencies looser.+- Fix typo in README.md option documentation.++### Remove+- Remove TOC, the hyperlinks weren't working on Hackage.++# 3.0.1 [2017-06-04]++### Fixed - Fixed CHANGELOG.md rendering for Hackage (see pull request [#106]). ### Added@@ -19,7 +28,7 @@ [#107]: https://github.com/lwm/tasty-discover/pull/107 [#106]: https://github.com/lwm/tasty-discover/pull/106 -# 3.0.0 [2017-05-03]+# 3.0.0 [2017-06-03] ### Added - Add --tree-display configuration option (see pull request [#103]).
README.md view
@@ -9,15 +9,6 @@ [tasty framework]: https://github.com/feuerbach/tasty -### Table Of Contents--- [Getting Started](#getting-started)-- [Examples](#examples)-- [Configuration](#configuration)-- [Change Log](#change-log)-- [Contributing](#contributing)-- [Acknowledgements](#acknowledgements)- # Getting Started 5 steps to tasty test discovery satori:@@ -100,7 +91,7 @@ - `--tree-display`: Display the test output results hierarchically. ## With Arguments-Example: `{-# OPTIONS_GHC -F -pgmF tasty-discover -optF --moduleSuffix=FooBar #-}`+Example: `{-# OPTIONS_GHC -F -pgmF tasty-discover -optF --module-suffix=FooBar #-}` - `--module-suffix`: Which test module suffix you wish to have discovered. - `--generated-module`: The name of the generated test module.
tasty-discover.cabal view
@@ -3,7 +3,7 @@ -- see: https://github.com/sol/hpack name: tasty-discover-version: 3.0.1+version: 3.0.2 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.