Hi Jörg,
Jörg Jahnke wrote:
Efficiency is important. Thus my insisting on first discussing and
selecting the tests
and then deciding how to deal with them. If you think that the 45 test
cases identified by the QA team are a proper selection we should have a
closer look on them and identify which code they test.
OK. I will ask Jogi to give some details on these tests here on the
mailing list.
We haven't identified the tests. The requirements was that they should
be "rock solid" and we have given those RESOURCE and MAIN FUNCTIONALITY
tests to customers and they were able to deal with them.
It makes sense to use firstly less than these ~45 and have a look if we
"stop the bleeding" [means many regressions on every MWS] or not. If not
we should enhance the test coverage. As I have written it is a
step-by-step process.
If we leave it as it is, we need the time to validate the defects in the
MWS with the defects in CWS everytime and have to filter where the diff is.
Cu,
Jogi
http://qa.openoffice.org/qatesttool
http://wiki.services.openoffice.org/wiki/User:Jsi
--
Sun Microsystems GmbH Joerg Sievers
Nagelsweg 55 Quality Assurance Engineer
20097 Hamburg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
