Subject: Committing tests
From: Keunwoo Lee (klee@cs.washington.edu)
Date: Mon Mar 12 2001 - 22:58:14 PST
Committing my mini-tests, even though they're trivial and do not work
without the rest of my code (which I am not yet committing), as a
suggestion for how people can begin putting handmade regression tests in
the whirlwind/tests directory.
The files and directories are as follows:
common.wil : common declarations (int4, etc.) needed by all tests
features/ : subdirectory containing a small files, each of which
tests one logical "feature" of the compiler.
test-base.wil : the baseline, always-run test that we will hopefully
keep working on every commit. Should "include" any files in features/
which we feel confident about.
full-test-base : a more obsessive and thorough set of tests, which
will exercise even features that we do not feel confident about, or
which are simply unimplemented. I think this will be useful because
we are making lots of compromises (or I am, anyway) in order to get
whirlwind working sooner: there are things that WIL should
theoretically be able to express that we will not support in version
1.0. But, we should still have something that exercises these
features. Right now I don't have anything in full-test-base that is
not in test-base.
Note that since I am not yet committing my current code, I have broken
my own pronouncement about test-base.wil, which is that it should
always contain code that successfully compiles. But, this is a
special case since I am suggesting how tests/ should work.
~k.lee
_______________________________________________
Cecil mailing list
Cecil@cs.washington.edu
http://majordomo.cs.washington.edu/mailman/listinfo/cecil
This archive was generated by hypermail 2b25 : Mon Mar 12 2001 - 22:59:04 PST