Hi André,
Andre Schnabel wrote:
[...]
- test case specifications for the new Features can be provided by Sun
QA-team
- these test cases can be adopted and expanded by testers from QA
project; these test case specifications should be a skeleton
Going through the feature issues, most of them have at least the
specification attached or linked. An experienced tester could start with
that.
If test case specifications are available, they should be linked from
the issue (or from the spec document). This could help to get more testers.
In the specifications there have to be a link to a test case. So this is
done, when a test case is written (generally it is a MUST to write a
test case specification for each new feature with a specification!).
- how the testing can be organized and where and how these test cases
can be stored should be discussed
This is still a problem :-( At the moment I think, that advertizing the
need of those tests would be a first step. The problem is still to
collect feedback about the tests. Ok .. we will have negative feedback
in Issue Tracker. But it's hard to tell, if we get no feedback, if this
is because we have only positive results or because nobody is testing.
But seems, this needs to wait until we have a great idea.
OK. This will be discussed seperately.
With this action, we should be able to find regressions, feature or
changes, which are not so welcome in OOo earlier. And perhaps we do
not need so much RC's anymore.
What do you think about the point above?
I'm all for it ;-)
Just one question ... should we start with this and give m180 (or the
next master build) some more attention (e.g. visible announcement at
qa.openoffice.org)?
Yes can start with m180. I talked with Joost and he told me, that all
features are documented in the release notes for each milestone. Do you
think, that is enough.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
