Skip to content
Snippets Groups Projects
  1. Jan 28, 2019
  2. Jan 24, 2019
    • Judah Jacobson's avatar
      Convert the test to a test-suite. (#110) · 3214a170
      Judah Jacobson authored
      This works with `stack` and `cabal new-test`.  The latter
      uses the `build-tool-depends` field to locate the binary.
      
      Also:
      - Remove the reference to the nonexistent main file on Windows.
      - Make the test binary return a nonzero exit code when it fails.
      
      Still TODO: test in CI.
      3214a170
  3. Jan 23, 2019
    • Kamil's avatar
      Define executable targets in the cabal file for tests (#103) · 4e7e0424
      Kamil authored
      This change is motivated to make it easier to run the unit tests:
      
      defined two executable targets in the cabal file
      added run_unit_tests.sh script
      one test is failing independent of the changes:
      
      ```
      Failure in: 0:interaction:2:tab completion:0
      tests/RunTTY.hs:106
      expected: ["dummy-\206\188\206\177\207\131/\r\nbar \207\130\206\181\207\129\207\132\r\n0:dummy-\206\188\206\177\207\131/"]
      but got: ["dummy-\206\188\a\a"]
      ```
      4e7e0424
  4. Jan 22, 2019
    • Judah Jacobson's avatar
      Add the new function `waitForAnyKey`. (#108) · 6b145aac
      Judah Jacobson authored
      Fixes #74 as well enough as Haskeline currently can.  It returns
      a `Bool` rather than `Maybe Key` since Haskeline doesn't expose its
      `Key` type.  But this should be enough for the "press any key to continue"
      functionality described in the feature request.
      6b145aac
  5. Jan 21, 2019
  6. Jan 17, 2019
  7. Dec 10, 2018
  8. Oct 20, 2018
  9. Oct 06, 2018
  10. Jun 24, 2018
  11. Jun 20, 2018
  12. Jun 18, 2018
  13. Jun 03, 2018
  14. Jun 02, 2018
  15. Apr 16, 2018
  16. Apr 10, 2018
  17. Dec 11, 2017
  18. Dec 02, 2017
  19. Nov 08, 2017
  20. Sep 22, 2017
  21. Sep 21, 2017
  22. Sep 20, 2017
  23. Aug 27, 2017
Loading