[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Unit testing of non-exported procedures
From: |
Evan Hanson |
Subject: |
Re: [Chicken-users] Unit testing of non-exported procedures |
Date: |
Wed, 27 Mar 2013 18:49:33 -0500 |
User-agent: |
OpenSMTPD enqueuer (Demoosh) |
Hi Matt,
A simple solution might be to keep your implementation in one file and
your module form in another that includes it. Then, your tests could
`include` or `load-relative` or whatever the implementation file rather
than the module, making all its definitions visible.
This may not work for your situation, but it's straightforward if you'll
always be testing with the source present.
Cheers,
Evan