(Created page with "QA Community Member Currently efforts within QA are split (at least informally) between testing and triage. The triaging piece used to be handled by the BugZappers group - wh...") |
No edit summary |
||
| Line 1: | Line 1: | ||
QA Community Member | = QA Community Member Merger = | ||
Currently efforts within QA are split (at least informally) between testing and triage. The triaging piece used to be handled by the BugZappers group - which is no longer active. But, we still need to triage bugs - so [[User:Johannbg | Johann]] came up with an idea to merge testing and triage. Below is a brief overview of what's been discussed. | |||
{| | {| | ||
|- | |- | ||
| Component 1 | | '''Component 1''' | ||
| Component 2 | | '''Component 2''' | ||
| Component 3 | | '''Component 3''' | ||
| Component 4 | | '''Component 4''' | ||
| Component 5 | | '''Component 5''' | ||
|- | |- | ||
| Test: Roshi | | ''Test'': Roshi | ||
| Triage: Viking-Ice | | ''Triage'': Viking-Ice | ||
| Test: Roshi | | ''Test'': Roshi | ||
| Triage: Viking-Ice | | ''Triage'': Viking-Ice | ||
| Test: Roshi | | ''Test'': Roshi | ||
|- | |- | ||
| Triage: Viking-Ice | | ''Triage'': Viking-Ice | ||
| Test: Roshi | | ''Test'': Roshi | ||
| Triage: Viking-Ice | | ''Triage'': Viking-Ice | ||
| Test: Roshi | | ''Test'': Roshi | ||
| Triage: Viking-Ice | | ''Triage'': Viking-Ice | ||
|} | |} | ||
Each Component in Base needs someone to test it and someone to traige bugs related to it. Making a schedule, or list like the one above with a team of 2 (that alternate testing and triage) working through the list helps provide solid QA coverage for all the components we have to test. | Each Component in Base needs someone to test it and someone to traige bugs related to it. Making a schedule, or list like the one above with a team of 2 (that alternate testing and triage) working through the list helps provide solid QA coverage for all the components we have to test. | ||
| Line 28: | Line 30: | ||
This pattern could be applied to all areas of QA. People just starting can simply walk through updates-testing providing karma and more experienced users can work on Rawhide. | This pattern could be applied to all areas of QA. People just starting can simply walk through updates-testing providing karma and more experienced users can work on Rawhide. | ||
To Do: | '''To Do''': | ||
Test plan | Test plan | ||
Latest revision as of 18:58, 24 January 2014
QA Community Member Merger
Currently efforts within QA are split (at least informally) between testing and triage. The triaging piece used to be handled by the BugZappers group - which is no longer active. But, we still need to triage bugs - so Johann came up with an idea to merge testing and triage. Below is a brief overview of what's been discussed.
| Component 1 | Component 2 | Component 3 | Component 4 | Component 5 |
| Test: Roshi | Triage: Viking-Ice | Test: Roshi | Triage: Viking-Ice | Test: Roshi |
| Triage: Viking-Ice | Test: Roshi | Triage: Viking-Ice | Test: Roshi | Triage: Viking-Ice |
Each Component in Base needs someone to test it and someone to traige bugs related to it. Making a schedule, or list like the one above with a team of 2 (that alternate testing and triage) working through the list helps provide solid QA coverage for all the components we have to test.
This pattern could be applied to all areas of QA. People just starting can simply walk through updates-testing providing karma and more experienced users can work on Rawhide.
To Do:
Test plan Come up with list of Components to start with (Likely comps groups) Determine best time period for a slot Figure out levels Gamification