Comments on: Simple unit testing with Chicken Scheme http://4.flowsnake.org/archives/45 A Pythoneer's adventures with Chicken Scheme. ^_^ And more. Wed, 07 Jan 2009 04:13:58 +0000 http://wordpress.org/?v=2.6.5 By: Hans Nowak http://4.flowsnake.org/archives/45#comment-44 Hans Nowak Tue, 29 Jan 2008 15:31:00 +0000 http://4.flowsnake.org/archives/45#comment-44 @Ian: Maybe I will. :) It should be an interesting project to do, and maybe to contribute (as an egg or otherwise). I'm not sure I know enough about all the details yet, though, like the docstrings. @Ian: Maybe I will. :) It should be an interesting project to do, and maybe to contribute (as an egg or otherwise). I'm not sure I know enough about all the details yet, though, like the docstrings.

]]> By: Ian Bicking http://4.flowsnake.org/archives/45#comment-43 Ian Bicking Tue, 29 Jan 2008 04:25:19 +0000 http://4.flowsnake.org/archives/45#comment-43 I harp on this frequently, but: write doctest for Scheme! It even has docstrings (though stand-alone files are also nice), repr, and a super-easy-to-use eval. And its tokenizer is also easy to use. It should be much easier to write than in Python. I harp on this frequently, but: write doctest for Scheme! It even has docstrings (though stand-alone files are also nice), repr, and a super-easy-to-use eval. And its tokenizer is also easy to use. It should be much easier to write than in Python.

]]> By: Kon Lovett http://4.flowsnake.org/archives/45#comment-22 Kon Lovett Tue, 22 Jan 2008 21:28:39 +0000 http://4.flowsnake.org/archives/45#comment-22 The "testbase" suite is a possibility. However I would never claim it to be "easy". Alex's "test" and Neil's "testeez" are much more approachable. Another pkg you might run into is "SchemeUnit". While not available for Chicken ("testbase" has similar facilities) you will come across it with PLT Scheme. I wrote "testbase" & use it for my eggs so there are a number of real-world examples. I don't have a configurable report generator, however there are a number of pre-defined available. Also "testbase", used with the testbase driver, will build a database of results. Flavor example: (use testbase testbase-output-compact) (define-test opcode-test "Opcodes" (initial (define (test-opcode opcode) (define test-name (sprintf "test opcode: ~s" opcode)) (expect-success test-name (member (opcode-type opcode) *opcode-types*))) ) (test/collect "All opcodes" (for-each (lambda (opcode) (collect-test (test-opcode opcode))) *opcodes*) ) ) (test::output-style-compact (opcode-test)) SUITE Passed: Opcodes CASE Passed: All opcodes EXPECTATION: test opcode: # Expect success Passed: test opcode: # EXPECTATION: test opcode: # Expect success Passed: test opcode: # EXPECTATION: test opcode: # Expect success Passed: test opcode: # ALL TESTS SUCCESSFUL! #t The "testbase" suite is a possibility. However I would never claim it to be "easy". Alex's "test" and Neil's "testeez" are much more approachable. Another pkg you might run into is "SchemeUnit". While not available for Chicken ("testbase" has similar facilities) you will come across it with PLT Scheme.

I wrote "testbase" & use it for my eggs so there are a number of real-world examples. I don't have a configurable report generator, however there are a number of pre-defined available. Also "testbase", used with the testbase driver, will build a database of results.

Flavor example:
(use testbase testbase-output-compact)
(define-test opcode-test "Opcodes"
(initial
(define (test-opcode opcode)
(define test-name (sprintf "test opcode: ~s" opcode))
(expect-success test-name (member (opcode-type opcode) *opcode-types*))) )

(test/collect "All opcodes"
(for-each (lambda (opcode) (collect-test (test-opcode opcode))) *opcodes*) ) )
(test::output-style-compact (opcode-test))

SUITE Passed: Opcodes

CASE Passed: All opcodes

EXPECTATION: test opcode: #
Expect success
Passed: test opcode: #

EXPECTATION: test opcode: #
Expect success
Passed: test opcode: #

EXPECTATION: test opcode: #
Expect success
Passed: test opcode: #

ALL TESTS SUCCESSFUL!
#t

]]>