Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
"Tobias C. Rittweiler" <tcr@...> writes:
> Isn't this worth one, or two test cases?
Yes! Yes please. (A large part of my recent development pain was
discovering that there were large swathes of untested codepaths, which I
therefore didn't feel safe about modifying until I wrote tests for them)
> I wonder how one would best write test cases involving the
> file-compiler. We really ought to have a COMPILE-FROM-STREAM which has
> file-compilation semantics!
In answer to the first half of the question: test files with names such
as xxx.pure-cload.lisp and xxx.impure-cload.lisp get compile-filed and
loaded; for explicitly testing return values of the file compiler, there
are test scripts such as tests/compiler.test.sh (with utility shell
functions in tests/expect.sh)