Public SourceMage Discussion List

[Ethan Grammatikidis <eekee57 AT fastmail.fm>]

On Mon, 18 May 2009 10:03:07 -0500
Mark Bainter <mbainter-smgl AT trampledstones.com> wrote:

> Remko van der Vossen [wich AT yuugen.jp] wrote:
> > On Mon, May 18, 2009 at 07:41:13AM +0200, Andraž 'ruskie' Levstik wrote:
> > In any case I would be all for adding a QA script to the spells. The
> > question however is what we will do with it for now, do we set up a
> > dedicated QA system casting spells and running QA scripts, do we rely on
> > the grimoire developers to run the QA scripts, do we make it a sorcery
> > option to run QA after every cast so that regular users can also help?
> 
> This would be the point of it in my opinion.   I agree that the
> developer should test it before committing, but that is only a test on a
> single set of hardware with a given build of SMGL.  With a QA test it
> can be checked under a number of different build conditions in an
> automated fashion. 

All sounds good to me, especially the point about QA increasing the testing.

One issue I can think of: If multiple spells are cast together, when should 
QA be run? If at the end of each individual cast (after FINAL) runtime deps 
may not be present. If all of the pending spells are cast before any QA is 
run what about spells who's QA involves some form of make test in the source 
tree?

Or have I missed the point of QA? :) Even if I have I'd like to see a means 
of running make test in those packages which support it.

-- 
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer