Comments on: Organising unit tests in Haskell http://blogs.linux.ie/balor/2009/07/05/organising-unit-tests-in-haskell/ We eat cats whilst you code. Thu, 17 May 2012 00:31:11 +0100 hourly 1 http://wordpress.org/?v=3.1.4 By: balor http://blogs.linux.ie/balor/2009/07/05/organising-unit-tests-in-haskell/comment-page-1/#comment-64377 balor Sun, 05 Jul 2009 23:18:23 +0000 http://blogs.linux.ie/balor/?p=273#comment-64377 I don't like to put my tests in the same module. Maybe it's an OO hangover. But I generally don't want to ship a test suite with the eventual product. So keeping the suite in a subdirectory means I can release the "product", rather than the development code, more easily. I don’t like to put my tests in the same module. Maybe it’s an OO hangover. But I generally don’t want to ship a test suite with the eventual product. So keeping the suite in a subdirectory means I can release the “product”, rather than the development code, more easily.

]]> By: Eric Kow http://blogs.linux.ie/balor/2009/07/05/organising-unit-tests-in-haskell/comment-page-1/#comment-64300 Eric Kow Sun, 05 Jul 2009 13:04:51 +0000 http://blogs.linux.ie/balor/?p=273#comment-64300 Also, if your tests are for one specific module (e.g, BuildNfa), you might consider just putting them in that same module. Then they can double as documentation and keep your tree simple. Also, if your tests are for one specific module (e.g, BuildNfa), you might consider just putting them in that same module. Then they can double as documentation and keep your tree simple.

]]> By: Eric Kow http://blogs.linux.ie/balor/2009/07/05/organising-unit-tests-in-haskell/comment-page-1/#comment-64299 Eric Kow Sun, 05 Jul 2009 13:02:36 +0000 http://blogs.linux.ie/balor/?p=273#comment-64299 Module names in Haskell start with a capital letter. It looks fine to me, although running a Haskell program from the shell (<code>runzeTests</code>) seems a bit complicated, when you could simply just <code> runTestTT TestBuildNfa.suite</code> directly. Also, with a couple of superficial modifications, you could switch to a proper test framework, namely <a href="http://batterseapower.github.com/test-framework/" rel="nofollow">test-framework</a> (this supesedes the testrunner package I previously mentioned). This buys you some nice reporting, the ability to group your tests, run them in parallel and eventually integrate QuickCheck tests when you work out a way to write them. Module names in Haskell start with a capital letter.

It looks fine to me, although running a Haskell program from the shell (runzeTests) seems a bit complicated, when you could simply just runTestTT TestBuildNfa.suite directly.

Also, with a couple of superficial modifications, you could switch to a proper test framework, namely test-framework (this supesedes the testrunner package I previously mentioned). This buys you some nice reporting, the ability to group your tests, run them in parallel and eventually integrate QuickCheck tests when you work out a way to write them.

]]> By: Aidan Delaney (balor) 's status on Sunday, 05-Jul-09 10:14:53 UTC - Identi.ca http://blogs.linux.ie/balor/2009/07/05/organising-unit-tests-in-haskell/comment-page-1/#comment-64276 Aidan Delaney (balor) 's status on Sunday, 05-Jul-09 10:14:53 UTC - Identi.ca Sun, 05 Jul 2009 10:14:58 +0000 http://blogs.linux.ie/balor/?p=273#comment-64276 [...] Organising Unit Tests in Haskell http://blogs.linux.ie/balor/2009/07/05/organising-unit-tests-in-haskell/ [...] [...] Organising Unit Tests in Haskell http://blogs.linux.ie/balor/2009/07/05/organising-unit-tests-in-haskell/ [...]

]]>