Hi QA project,
in February this year Andre Schnabel and Jacqueline Rahemipour were in
Hamburg to meet the Sun QA team. One point we talked about was to
extend the QA project for testing of general test cases, features etc.
On the one hand they found the idea good on the other hand they did not
know, how this could be organized in the huge project with many
different language QA teams.
After some very time consuming releases I want to discuss this challenge
with the whole project.
What is the plan in my head ?
- Increase the quality of OOo
- new Feature are often tested once in CWS and after integration into
master build; only when bug fixes or additional features are
integrate in this area, the feature will be tested completely again
=> but mostly not on regular base (no time)
- only when an automated test script exists, features are tested on
regular base!
- if regressions comes into a feature, the bugs were found by
accident, mostly they aren't found by general testing
- a general testing of new features with manual test cases is time
consuming and needs a lot of resources
- only continuous testing could guarantee a high and stable quality of
new features
- Bring test case specifications from Sun team to the OOo QA project
- To bring a new feature into OOo a specification is needed. To
increase the quality of these features it is necessarily to write a
test case specification based on the original specification or write
a new automated test script.
- The Sun QA team wrote for OOo2.0 some test case specifications
for areas, where automated testing isn't so effective or where we
do not had the resources to write new automated test scripts.
- In the first shot Sun QA team want to bring some test cases (perhaps
5 per application) for highly important features to OOo
How can general testing be realized ?
- integrate general test case specifications into TCM
- until now TCM isn't feasible for longer test cases with formating
- a possible solution is to integrate links to web sides with the
test case specifications into TCM (web sides are saved via CVS)
- TCM should be the tooling to organize results of test runs
- the general test case specifications doesn't test features which
are language dependent.
- It implies, it isn't needed, that each Language QA Team have to run
all test cases. The testing can be organized over Language QA Team
borders away - if possible!
- It isn't needed to translate each test case specification in each
language
- someone have to organize the testing between the teams or with single
testers
- perhaps single testers can be responsible to testing areas
- each tester can organize the testing cycle by his-/himself
- only liberal time lines are communicated to communicate the results
into TCM
- the barrier to write test case specifications by community will be
perhaps lower, when more support will be given
- adapt and extend existing test case specifications
- write new test case specifications with a template/skeleton
A possible solution was announced by Chris Lukasiak yesterday. He
presented test case specifications and solutions for the 'New dba QA
project'. It can be found http://dba.openoffice.org/QA/index.html.
Please start with me and others the discussion about feasible solutions
and if my proposal can improve and extend the OOo QA project. There will
be many things to be organized, but I we should start soon.
Regards,
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
