Re: [jamboost] On testing

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-03-27 10:51:44

Steven Knight wrote:

> > In detail, I will:
> > 1. Add a method to copy a an existing tree to the temporary area
> > 2. Add a methon "run_build_system" which will
> > a) call 'run' method
> > b) traverse that temporary area and create in-memory tree
> > representation
> > c) Compare the tree representation with the previous one, to
> > find additions/touches etc.
> > 3. Add a number of methods which test tree differences against
> > expected, for example:
> > expect_addition
> > expect_touch
> > expect_nothing_more
>
> I like the sound of all of this a lot. I think the addition of methods
> to make it easier to work with an external directory tree in the way you
> describe would be extremely valuable. I'd be very glad to work with
> you on this and fold any of your method that apply to the underlying
> functionality into TestCmd.py, in an anticipation of releasing it for
> public consumption on the Vaults of Parnassus.
>
> I've always intended for TestCmd.py to be a very generic interface that
> would support multiple testing methodologies. It's just that it's not
> hard to lose track of that goal when you only have your own testing
> methodology to support... :-)

Great. I'm about to start working at it. So far it seems like deriving from 
TestCmd and adding a few methods will work just fine. I'll possibly also need 
to redefine "fail_test" method and others similar, in case I decide to 
integrate the tests with QMTest, where reporting via printing to stdout is 
not appropriate.

I'll post another message when (hopefully soon), everything will be finished.

- Volodya