Hi Laurent,
Laurent Godard schrieb:
the first question i have is when and who writes the testools .bas files
?
Test Automators of the Quality Assurance.
at development stage ? at RC release time ?
More than one answer, depending on WHAT kind of test.
1. At development stage (CWS)
-> for resource tests of new / changed features
2. By request of the QA
-> for functional tests
3. Own initiative
-> if there are problems, white areas of no testing,
the test automators decide often to create test cases
i plan to gather some volunteers to do a "continuous testing effort"
each time a version is built (no matter if it is a RC or a developper
snapshot), the testools would be run and error reported at early stage.
Great idea!
some french people volunteered and i think we can start an
experimentation on this. The main interrest is to do this out of the
scope of a release to inform the developpers asap that something went
wrong so that the ideas are fresh in their mind
That's what we also do here in the Automated GUI Testing project at Sun.
OOo is supporting more platforms than StarOffice, so it would make sense
to share the results of that work. That was also the idea of a "Google
Summer Of Code" project but it has not been accepted by Google...
Maybe we (also Thorsten Bosbach from the same project team will be
there) can talk about your idea in Lyon face to face?
Cu,
Jogi
--
===============================================================
Sun Microsystems GmbH Joerg Sievers
20097 Hamburg Quality Assurance Engineer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
