Joerg Sievers wrote:
- 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;
Do we have some statistics in which areas we have what amount of
regressions ?
For example I would think that regression caused by broken resources
doesn't occur that much any more, are also easy to find by broad
testing. On the other hand I could image that regressions in document
layout do occur much more often and would be reported much more later
than broken resources ?
What about Wizards, System Integration, OLE, foreign formats, where do
we have the biggest problems ? Can we use there more faster tests than
we have with the testtool ?
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
