On 26 Jul 2001, at 10:03, Svein Erling Tysvær wrote:

> In a former job I did some testing for a large bank deposit system
> using a tool for on-line testing automation. I don't remember its
> name, but it was a very bad experience - albeit partly due to us using
> it for a purpose it was not designed to handle.
>
> Nowadays I only write small, internal programs for The Cancer Registry
> of Norway, basically just requiring me to try it once (sometimes I
> don't even get to do that) before considering it finished. My programs
> are not flawless, but whenever an error is discovered - I can normally
> fix it within minutes or hours and the users are happy.
>
> My point is that testing is such a wide subject, and that requirements
> vary a lot. In general, I guess test suites could be invaluable for
> batch testing of large systems - whereas testing of online programs is
> far more difficult. The first thing you ought to find out is what you
> want to test. >From there it will be easier to ask questions to see if
> someone has been in a similar situation and may offer some advice.
> Besides, it will clarify for yourself what your requirements should
> be.

This is true, I am starting a new project, and would rather design
the testing procedure along with the application.

I thought automating it would be cool, and you could look for
predictable results.

> I'm looking forward to the rest of this thread - it is an interesting
> subject that maybe will lead to a new branch of IBO components?
>

True, a testing component, takes a specialised script, and executes
it. You could take an empty database, run the script, which includes
some reports, print the reports, and examine the results.

Paul

Paul Schmidt,
Tricat Technologies
Email: paul@...
Website: www.tricattechnologies.com