homepage: https://gitlab.com/igrep/main-tester#readme
changelog-type: markdown
hash: e42ac2d5d813470bbded1f23a2967325ee11d026c508a6d3de0bbded8df35973
test-bench-deps:
  bytestring: -any
  base: -any
  hspec: -any
  text: -any
  hspec-core: -any
  doctest: -any
  main-tester: -any
  QuickCheck: -any
maintainer: whosekiteneverfly@gmail.com
synopsis: Capture stdout/stderr/exit code, and replace stdin of your main function.
changelog: ! '# 0.1.0.0


  - Initial release.

'
basic-deps:
  bytestring: -any
  base: ! '>=4.7 && <5'
  directory: -any
all-versions:
- '0.1.0.0'
author: Yuji Yamamoto
latest: '0.1.0.0'
description-type: markdown
description: ! "# main-tester\n\nCapture stdout/stderr/exit code, and replace stdin
  of your main function.\n\n## Why?\n\nAgainst the best practice, I often prefer large,
  end-to-end (E2E) tests.  \nBecause:\n\n- E2E tests can directly test your users'
  requirement.\n- E2E tests can detect bugs caused by misassumption of external components\n
  \   - Which happenes relatively more often than the others, according to my experience.\n-
  I often write small programs where E2E tests are sufficient.\n\nThis library main-tester
  provides utility functions for E2E testing of your CLI applications.  \nWith main-tester,
  You can test your apps with arbitrary stdin data, check their output and exit code.\n\n##
  Comparison with [silently](https://hackage.haskell.org/package/silently) and [System.IO.Fake](https://hackage.haskell.org/package/imperative-edsl-0.7.1/docs/System-IO-Fake.html)\n\n-
  Can test exit code of your main.\n- All input and outputs are strict bytestrings
  except the command line arguments, which is very important when testing with non-UTF8
  input and output.\n- Currently doesn't support suppressing stdout and stderr (Pull
  request welcome!).\n"
license-name: Apache-2.0

Update from Hackage at 2018-04-04T23:41:34Z
Update from Hackage at 2018-04-04T23:41:34Z
