On 11 August 2011 05:17, John Millikin jmilli...@gmail.com wrote:
This is just a quick package I whipped up out of frustration with
test-framework scrolling an error message out of sight, for the
millionth time.
Patches to make test-framework less noisy (either by default or with a
flag) will
Hi John,
I am wondering if you have seen the hspec package? [1] It seems to solve all
the problems you are with chell, including that it silences Hunit output. We
are using it for all the Yesod tests now.
Thanks,
Greg Weber
[1]:
I have, but it's not quite what I'm looking for:
- I don't want to silence HUnit's output, I just don't want anything
to show on the console when a test *passes*. Showing output on a
failure is good.
- I'm not interested in BDD. Not to say it's not useful, but it
doesn't match my style of
I tried, actually, but couldn't figure out how to separate running the
test from printing its output. All the attempted patches turned into
huge refactoring marathons.
When given the choice between sending a huge replace all your code
with my code patch, and just releasing a separate package, I
It silences HUnit's output, but will tell you what happens when there is a
failure- which I think is what you want. There are a few available output
formatters if you don't like the default output, or you can write your own
output formatter.
BDD is really a red herring. Instead of using function
On Thu, Aug 11, 2011 at 07:52, Greg Weber g...@gregweber.info wrote:
It silences HUnit's output, but will tell you what happens when there is a
failure- which I think is what you want. There are a few available output
formatters if you don't like the default output, or you can write your own
I am confused also, as to both what output you don't like that motivated
chell and what exactly hspec silences :) Suffice to say I am able to get a
small relevant error message on failure with hspec. I am adding the hspec
maintainer to this e-mail- he can answer any of your questions.
On Thu, Aug
On Thu, Aug 11, 2011 at 08:17, Greg Weber g...@gregweber.info wrote:
I am confused also, as to both what output you don't like that motivated
chell and what exactly hspec silences :) Suffice to say I am able to get a
small relevant error message on failure with hspec. I am adding the hspec
Is this different than the --hide-successes flag for test-framework? Looks
like it was added a few months back:
https://github.com/batterseapower/test-framework/commit/afd7eeced9a4777293af1e17eadab4bf485fd98f
-n
On Thu, Aug 11, 2011 at 8:21 AM, John Millikin jmilli...@gmail.com wrote:
The
Possible -- I ran into dependency conflicts between
t-f/t-f-q/quickcheck when trying to migrate to test-framework 0.4, so
I clamped all my test subprojects to 0.3.
On Thu, Aug 11, 2011 at 09:09, Nathan Howell nathan.d.how...@gmail.com wrote:
Is this different than the --hide-successes flag for
As Greg pointed out, HSpec does have an option to output just the failed tests.
I looked at the example on the Chell project home page and converted the
example tests into these hspec style specs:
import Test.Hspec (Specs, descriptions, describe, it)
import Test.Hspec.Runner
On 11 August 2011 15:49, John Millikin jmilli...@gmail.com wrote:
I tried, actually, but couldn't figure out how to separate running the
test from printing its output. All the attempted patches turned into
huge refactoring marathons.
Just FYI test-framework already has exactly this split
Homepage: https://john-millikin.com/software/chell/
Hackage: http://hackage.haskell.org/package/chell
This is just a quick package I whipped up out of frustration with
test-framework scrolling an error message out of sight, for the
millionth time.
Chell has the same general purpose
13 matches
Mail list logo
