|
|
| Line 1: |
Line 1: |
| − | <div align="center"><font size="+1">'OOo QA Reloaded' Onepager</font>
| + | [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-Onepager.odt Onepager] |
| − | <br>
| + | |
| − | <font size="-1"><i>by Chris Lukasiak</i></font></div>
| + | |
| − | <br>
| + | |
| − | <div align="center">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)</div>
| + | |
| − | <br>
| + | |
| − | <div align="center"><b>support/reorganize community</b><br>
| + | |
| − | (get new user / support old qa members)</div><br>
| + | |
| − | | + | |
| − | <ul>
| + | |
| − | make test process easier and more transparent<br>
| + | |
| − | pick up unexperienced user<br>
| + | |
| − | establish qa participation steps (report bugs/execute ts/join qa)<br>
| + | |
| − | make project more popular / visible<br>
| + | |
| − | give qa more structure, clear responsibility (hierarchy?)<br>
| + | |
| − | bind older qa member in new roles / reorganize qa members in app. chapters<br>
| + | |
| − | </ul><br>
| + | |
| − | | + | |
| − | <b><div align="center">improve qa process</div></b>
| + | |
| − | <ul><br>
| + | |
| − | define test process (something between so qa and oo language testing)<br>
| + | |
| − | connect single parts (from ts to green state of tested version)<br>
| + | |
| − | give testcase specification (like used in in so qa)<br>
| + | |
| − | give further info (to have a main info point for everything)<br>
| + | |
| − | fit tcm tool (is designed for language testing and must be reworked)<br>
| + | |
| − | give better overview of teststate / issues etc. (at the moment only at the tcm tool)
| + | |
| − | </ul><br>
| + | |
| − | | + | |
| − | <b><div align="center">establish new test cycle</div></b>
| + | |
| − | <br>
| + | |
| − | <div align="center">(similar to so qa test process release)<br>
| + | |
| − | new version available<br>
| + | |
| − | qa leads trigger qa team members<br>
| + | |
| − | qa team members execute defined tests<br>
| + | |
| − | qa team members give result in tooling (tcm?)<br>
| + | |
| − | results can be seen in overview matrix (todo check)<br>
| + | |
| − | version is rateable if deliverable or not<br>
| + | |
| − | qa lead can acknowledge</div>
| + | |
| − | | + | |
| − | | + | |
| − | <b><div align="center">project in five steps</div></b>
| + | |
| − | <br>
| + | |
| − | <ul>
| + | |
| − | 1. restructure QA starter page<br>
| + | |
| − | 2. establish testplan specifications on oo wicki<br>
| + | |
| − | 3. prepare TCM for testplan specification and QA process<br>
| + | |
| − | 4. create overview matrix<br>
| + | |
| − | 5. make project more popular<br>
| + | |
| − | </ul>
| + | |
