Hi,
Soon we will have the first Release Candidate (RC) for OpenOffice.org
2.0.4. In the past I have heard by Andre Schnabel that the testing and
release of a RC or the final bits took very long time. One reason was
the huge time investment to run as many automated test scripts.
Sun's automated GUI testing team want to support the release testing of
the localized builds on OOo.
Sun's StarOffice/StarSuite (the Sun branded build of OOo) automated GUI
testing will be done on each Sun supported platform [1] and language [2]
for each RC.
A subset of that test scripts guarantees that the most resources of the
builds are correct. In a time frame of ~2 days the automated GUI testing
team can give an approval for the general functionality of a localized
build.
StarOffice, StarSuite and OpenOffice.org are being build from the same
code line. Therefore the results of the automated GUI testing on
StarOffice/StarSuite and the OOo builds are nearly the same. If the
automated GUI testing of StarOffice didn't find defects the test scripts
won't find new defects on OOo in the general functionality and vice versa.
If Sun's automated GUI testing team will send out an approval of the Sun
supported platforms and languages the test results are the same as for
the OOo bits. This approval is only for the general functionality and
the OOo install sets built by Sun.
To release an install set OOo sanity checks needed to be sure that the
delivered build has been done correctly. What has to be done in a sanity
check should be discussed by the OOo QA project.
Should Sun's automated GUI testing team give such approvals for the
upcoming release? Would this be helpful to increase the release cycle on
OOo?
Comments are welcome!
Regards,
Thorsten
[1] : Solaris SPARC, Solaris x86, Windows and Linux - not deb-packages
[2] : English (US), German, French, Italian, Netherlands, Russian,
Polish, Spanish, Swedish, Hungary, Brazilian Portuguese, Korean,
Japanese, Chinese (simplify), Chinese (traditional)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
