RE: How to test a service program

[David FOXWELL <David.FOXWELL@xxxxxxxxx>]

> -----Message d'origine-----
> De la part de Scott Klement
> Objet : Re: How to test a service program
>
> So you want to use unit testing to prove that your service
> program's subprocedures are stateless?
>
> Or are you saying that your routines are stateful, and you
> want to test that different sets of related routines won't
> interfere with other sets of related routines?

Both. I think! That might lead me to another thread : what techniques are used or should be used to maintain state? Global variables? Static variables? A procedure designed just to maintain variables about state?


Thanks everyone, I'm actually interested to know how others executed their tests. At the moment, our standard routine will initialise everything modified by the test, then after each procedure the results are copied before executing the next procedure. For example, if File F1 is modified by P1 and P2, it will be copied to a temporary file F1_P1 before execution of P2. Then after P2 a copy to F1_P2 would be made. A program to compare the files is run at the end of all the tests. Programmers seem to find this a little confusing, and wonder how efficient this technique really is. So, I really would like to know how you guys did things.