diff --git a/CHANGELOG.md b/CHANGELOG.md
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -8,12 +8,24 @@
 [Keep a Changelog]: http://keepachangelog.com/
 [Semantic Versioning]: http://semver.org/
 
+# 4.1.4 [2018-02-25]
+
+## Added
+- Windows OS continuous integration build (see pull request [#136]).
+
+## Fixed
+- Test failure related to path handling on Windows OS (see pull request [#136]).
+- Resolved upstream tasty-hedgehog nightly blocking issue (see issue [#131]).
+
+[#136]: https://github.com/lwm/tasty-discover/pull/136
+[#131]: https://github.com/lwm/tasty-discover/issues/131
+
 # 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.
+[#132]: https://github.com/lwm/tasty-discover/pull/132
 
 # 4.1.2 [2017-12-19]
 
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -6,8 +6,16 @@
 
 # tasty-discover
 
-Automatic test discovery and runner for the [tasty framework].
+Haskell auto-magic test discovery and runner for the [tasty framework].
 
+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
+files. Tasty ingredients are included along with various configuration options
+for different use cases.
+
+See below for full documentation and examples.
+
 [tasty framework]: https://github.com/feuerbach/tasty
 
 # Getting Started
@@ -15,7 +23,7 @@
 There's 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-test-suite)
+  2. [Mark the driver file as the `main-is` in the test suite](#configure-cabal-or-hpack-test-suite)
   3. [Mark tests with the correct prefixes](#write-tests)
   4. [Customise test discovery as needed](#customise-discovery)
 
@@ -33,7 +41,7 @@
 {-# OPTIONS_GHC -F -pgmF tasty-discover #-}
 ```
 
-## Configure Cabal Test Suite
+## 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
@@ -42,7 +50,7 @@
 ```
 test-suite test
   main-is: Driver.hs
-  hs-source-dirs: tests
+  hs-source-dirs: test
   build-depends: base
 ```
 
diff --git a/library/Test/Tasty/Generator.hs b/library/Test/Tasty/Generator.hs
--- a/library/Test/Tasty/Generator.hs
+++ b/library/Test/Tasty/Generator.hs
@@ -26,7 +26,7 @@
 import           Data.Function   (on)
 import           Data.List       (find, groupBy, isPrefixOf, sortOn)
 import           Data.Maybe      (fromJust)
-import           System.FilePath (dropExtension, pathSeparator)
+import           System.FilePath (dropExtension, isPathSeparator)
 
 -- | The test type.
 data Test = Test
@@ -36,8 +36,8 @@
 
 -- | 'Test' constructor.
 mkTest :: FilePath -> String -> Test
-mkTest = Test . chooser pathSeparator '.' . dropExtension
-  where chooser c1 c2 = map $ \c3 -> if c3 == c1 then c2 else c3
+mkTest = Test . replacePathSepTo '.' . dropExtension
+  where replacePathSepTo c1 = map $ \c2 -> if isPathSeparator c2 then c1 else c2
 
 -- | The generator type.
 data Generator = Generator
diff --git a/tasty-discover.cabal b/tasty-discover.cabal
--- a/tasty-discover.cabal
+++ b/tasty-discover.cabal
@@ -2,10 +2,10 @@
 --
 -- see: https://github.com/sol/hpack
 --
--- hash: 5e21264f08d3ea239d539e1a1ee915ebaee0edd7c09319014e9fad439b1f9f00
+-- hash: 67adeac3d527af02d5415e0844c7369b646634800881dc80a115532354bdb1da
 
 name:           tasty-discover
-version:        4.1.3
+version:        4.1.4
 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.