Re: emacs test suite

[Kim F. Storm]

Jason Rumney <address@hidden> writes:

> Robert Anderson <address@hidden> writes:
> 
> > > That's cool, but why do you need the branch to be local?
> > 
> > Well, I don't "need" it to be - this is only a matter of convenience. 
> > But it would be nice if this didn't even require discussion or Richard
> > having to make a decision apriori about whether my work is credible
> > before he has even seen it.  If the branch was local, I would just get
> > to work, and everyone could worry about these decisions later when it
> > was more than vaporware, saving valuable coordinate effort.
> 
> Read the section of the CVS manual about vendor branches. Perhaps
> that would give the functionality you want.

If we keep the test suite in a separate directory tree, e.g. emacs/test,
I don't see *any* reason to make CVS branches to place the test suite in
CVS; like the emacs/admin directory, we don't have to distribute the
test scripts with emacs, unless we want to do that.

But if we get a substancial amount of tests, I think that advising the
user to run the test suite after building/installing emacs on a new
system would be a good thing.

Something simple like "make test" would be a good interface.

In addition, I believe that all of us write small scripts / sample
code to test and debug various things, so if we had a test/manual
directory below test/, we could put our own informal tests there --
and maybe our "auto-test experts" could pick up that work and
integrate it in the auto tests.

-- 
Kim F. Storm <address@hidden> http://www.cua.dk