Hi,
Kazunari Hirano wrote:
Will your de team use automation tool for 1.1.5rc2 QA?
Yes.
For windows you will need to use the tool from the website
(http://qa.openoffice.org/qatesttool/11beta/tt_645m5_windows.tar.gz)
as the testtool shipped with 1.1.5 will crash when trying to run the tests.
We will run at least following scripts:
- framework/first/first.bas
- framework/first/topten.bas
- writer/update/w_updt.bas
- calc/update/c_updt.bas
- graphics/update/i_updt.bas
- graphics/update/d_updt.bas
Scripts can be checked out from cvs component qa/qatesttool with tag
StarOffice7
Does the automation tool cover all the test cases in:
http://qa.openoffice.org/testcase/index.html
No, installation tests are not covered for instance, print tests as well
(at least not by the scripts I mentioned).
But the most important things to me, why manual testing is neccesary:
- testtool does not "know" what it is doing
- testtool does always the same things (no real user would do so)
- testtool has no eyes to look at the frontend or printout (so .. it can
tell, that a file is opened, but it cannot tell, if colors are displayed
well)
but what I would leave out from the manual tests are the file type tests
(they just say save / reopen .. that's something testtool does for the
common filetypes .. and it's time consuming whe done manually)
BTW.: It was a good idea, if some people go through themanual tests even
for the english build. So we have mr people who knwo what these tests
are about and can help adopting the testcases for 2.0.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
