QA reloaded

From Apache OpenOffice Wiki
Revision as of 16:15, 20 February 2007 by Clu (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
'OOo QA Reloaded' Onepager


by Chris Lukasiak


motivation: support vibrant community & improve oo qa process on oo

(qa is the most vibrating part of oo, so it should get more popular / visible) support/reorganize community + improve qa process -> create new test cycle

(to establish similar structure like proven in so qa)


support/reorganize community
(get new user / support old qa members)

    make test process easier and more transparent
    pick up unexperienced user
    establish qa participation steps (report bugs/execute ts/join qa)
    make project more popular / visible
    give qa more structure, clear responsibility (hierarchy?)
    bind older qa member in new roles / reorganize qa members in app. chapters

improve qa process

    define test process (something between so qa and oo language testing)
    connect single parts (from ts to green state of tested version)
    give testcase specification (like used in in so qa)
    give further info (to have a main info point for everything)
    fit tcm tool (is designed for language testing and must be reworked)
    give better overview of teststate / issues etc. (at the moment only at the tcm tool)

establish new test cycle


(similar to so qa test process release)

new version available
qa leads trigger qa team members
qa team members execute defined tests
qa team members give result in tooling (tcm?)
results can be seen in overview matrix (todo check)
version is rateable if deliverable or not

qa lead can acknowledge


project in five steps


    1. restructure QA starter page
    2. establish testplan specifications on oo wicki
    3. prepare TCM for testplan specification and QA process
    4. create overview matrix
    5. make project more popular
Personal tools