HTF 0.13.2.1 → 0.13.2.2
raw patch · 3 files changed
+8/−6 lines, 3 filesPVP ok
version bump matches the API change (PVP)
API changes (from Hackage documentation)
Files
- ChangeLog +3/−0
- HTF.cabal +1/−1
- Test/Framework/Tutorial.hs +4/−5
ChangeLog view
@@ -1,3 +1,6 @@+* 0.13.2.{0,1,2} (2017-08-6)+ - various build and documentation fixes and improvements+ * 0.13.1.0 (2015-08-21) - resolved compile error with HUnit == 1.3.0.0
HTF.cabal view
@@ -1,5 +1,5 @@ Name: HTF-Version: 0.13.2.1+Version: 0.13.2.2 License: LGPL License-File: LICENSE Copyright: (c) 2005-2015 Stefan Wehr
Test/Framework/Tutorial.hs view
@@ -90,7 +90,7 @@ Test-Suite tutorial Type: exitcode-stdio-1.0 Main-is: Tutorial.hs- Build-depends: base == 4.*, HTF == 0.10.*+ Build-depends: base, HTF Default-language: Haskell2010 @ @@ -207,7 +207,7 @@ split the tests into several modules. For example, suppose your library contains of two modules @MyPkg.A@ and @MyPkg.B@, each containing test functions. You can find a slightly extended of this scenario in the samples directory-of the HTF source tree, see <https://github.com/skogsbaer/HTF/tree/master/sample>.)+of the HTF source tree, see <https://github.com/skogsbaer/HTF/tree/master/sample>. File @MyPkg/A.hs@ @@ -243,9 +243,9 @@ For module @MyPkg.A@, the @htfpp@ preprocessor collects the modules' testcases into a variable @htf_MyPkg_A_thisModulesTests@ and defines a-preprocessor token @thisModulesTests@ as a shorthand for this variable.+preprocessor token @htf_thisModulesTests@ as a shorthand for this variable. Thus, to expose all HTF tests defined in @MyPkg.A@, we only-need to put @thisModulesTests@ into the export list. The same holds+need to put @htf_thisModulesTests@ into the export list. The same holds analogously for module @MyPkg.B@. To execute all tests defined in these two modules, you would create@@ -263,7 +263,6 @@ module Main where import Test.Framework-import Test.Framework.BlackBoxTest import {-@ HTF_TESTS @-} MyPkg.A import {-@ HTF_TESTS @-} MyPkg.B