Re: [HUnit-users] how do you use HUnit?

[Shae M. E. <sh...@Sc...>]

Dean Herington <her...@cs...> writes:

> I'm not sure I understand what you mean by already existing before test.
> That the function must be defined for compilation to succeed?  If that's
> what you mean, I don't think Haskell would differ from any other
> statically typed language, such as Java.  (A dynamically typed language
> might allow execution to begin without all referenced functions being
> defined.  Is this the case with Python?)

Not all dynamically typed languages allow that, but Python does.

> If you're bothered by having to create stubs in Haskell, note that they
> can be more concise than in any other language I know:
> 
>   someFunction = undefined

This is very nifty, it's exactly what I need. Thanks!

> Although I've not had much experience doing Beck-style unit testing, I
> imagine that I do in Haskell pretty much what one does in any language.  I
> write a/some test(s), implying some feature(s) of the interface to the
> unit under construction, then code enough of the implementation for the
> test to pass (which naturally progresses from fixing compilation errors to
> fixing execution errors).  I then repeat as needed to evolve the unit.

Yup, that sounds the same.

Hey, you mentioned that you have PyUnit style output, could I get a copy of
that code?

thanks,
-- 
Shae Matijs Erisson - http://www.webwitches.com/~shae/
<radix> shapr: I think you *are* a purist :)
<radix> shapr: it's just that you're morally against unstable software, instead
        of morally against MS, or non-free software, or whatnot.