Hi Mathias,
Mathias Bauer wrote:
Of course. And I'm still waiting to become convinced that the level of
testing that you suggest or more exactly the way it is implemented has
enough value to judge the effort.
So let's see how the tests look that will be provided. I hope that
someone will be able to explain what these tests are trying to examine
so that we can judge whether they make sense as a mandatory regression test.
In general:
- are all modules of the software package startable and are the main
features working (Writer, Calc, Impres, ... Base, Help, Basic, Java,
... Tools / Options settings) => first.bas, topten.bas
- if a resource file is broken or missing the office will crash if you
open the affected dialog; that's what these resource tests are doing:
Open all dialogs once, click on every button and leave all dialogs
with Cancel
- a list of business cards, a list of colors, a list of filters, a name
of filters, list of OLE objects ... is this list the same as
we expect? If not the user of an office application would run into
trouble to use it, e.g. he can not insert a chart, a formula etc.
- main functionality like loading and saving documents in different
formats is being tested; editing, cut, copy paste in different
formats; inserting images;
The collected tests, which should be "rock solid", have had these goals
in the past.
Be sure that we do nothing special because also the literature [1] and
well known software quality sites [2] recommending these steps.
HTH
Jogi
[1] Software Test Automation; Fewester&Graham
[2] http://www.stickyminds.com
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]
