Difference between revisions of "QA/QA Tasks"
From Apache OpenOffice Wiki
< QA
(→Intermediate) |
|||
| (124 intermediate revisions by 10 users not shown) | |||
| Line 1: | Line 1: | ||
| − | ''' | + | {{DISPLAYTITLE: QA Tasks}} |
| + | '''Welcome''' | ||
| − | + | Welcome to Apache OpenOffice(aka AOO) community. As QA we are helping improve AOO product quality. In generally, we are working on defect handling, manual test, and automation test. If you are interest in QA and willing to make AOO better, don’t hesitate to work with us and contribute your idea and your effort. | |
| − | + | QA volunteers please find tasks here: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | {| width="50%" class="wikitable" | |
| − | {| | + | |+ '''QA Task List''' |
|- | |- | ||
| − | ! Task | + | ! Task Type |
| − | ! | + | ! Task Link |
| − | ! | + | ! Update Date |
| − | + | ||
| − | + | ||
|- | |- | ||
| − | | | + | | Defect Task |
| − | | | + | | [[QA/Tasks/DefectTask]] |
| − | | | + | | Last Update 2012/11/19 |
| − | + | ||
| − | + | ||
|- | |- | ||
| − | | | + | | Test Case Task |
| − | + | | [[QA/Tasks/TestcaseTask]] | |
| − | + | | Last Update 2012/11/20 | |
| − | | | + | |
| − | | | + | |
|- | |- | ||
| − | | | + | | Automation Scripts Task |
| − | + | | *placeholder* | |
| − | + | | | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | | | + | |
| − | | | + | |
|} | |} | ||
| − | == | + | |
| − | + | '''Following reference for QA tasks''' | |
| − | + | ||
| − | + | =Working with defect= | |
| − | + | ||
| − | + | ==Confirm “UNCONFIRMED" defect== | |
| − | + | ||
| − | + | # Reading defect description carefully to get understand essential of the problem. | |
| − | + | # Based on the information provided verify whether the issue can be reproduced against latest build on all supported OS( the purpose of doing that is make sure whether the problem is OS independent). | |
| − | + | # Identify regression. Try the defect against some old builds, e.g. released milestone build, to verify if the problem can also be reproduced too. If no, that means the issue is introduced after that build. This will help developer to locate how the defect is introduced. | |
| − | + | # Do problem determination (PD). After reproduce defect, analysis defect symptom and function implementation try to give suggestion from QA/end user perspective. | |
| − | + | # If the problem can be reproduced, change defect status to “CONFIRMED”, otherwise communicate with reporter to figure out the reproduce steps. | |
| − | + | ||
| − | + | ==Verify “RESOLVED” defect== | |
| − | + | ||
| − | + | # Get latest build which include the fix. | |
| − | + | # Follow the reproduce steps on the OS which issue has been reported on, verify if the defect is able to be reproduced or not. | |
| − | + | # If the defect cannot be reproduce, then update your verification result to defect’s comments. | |
| − | + | # Based on your knowledge to identify which function area may be impacted by this bug fix to do impact testing. | |
| − | + | # If no problem found in impact testing, update your test result to defect’s comments. Otherwise reject the defect or accept this fix and open another new defect for the issue just found. | |
| − | + | # With all verify/test is passed, change defect status to “VERIFIED” and then change it to “CLOSED” | |
| − | + | ||
| − | + | ==Open new defect== | |
| − | + | ||
| − | + | # When encounter problem while testing product functionality, e.g. running test case, or verifying defect, following this guide to fire bug [[QA/HowToFileIssue]] | |
| − | + | ||
| − | + | =Working with manual testing= | |
| − | + | ||
| − | + | In AOO project, all manual testing assets, e.g. test case, test execution are store in Testlink system(http://aootesting.adfinis-sygroup.org/index.php) , with this system we can | |
| − | + | ||
| − | + | # Perform test case manually. | |
| − | + | # Write functionality test case | |
| − | + | ||
| − | + | For Testlink system usage guide, please refer to [[QA/Testlink]] | |
| − | + | ||
| − | + | For how to write test case, please refer to [[QA/Testcase/How_to_write_test_case]] and sample test case [[QA/Testcase/Sample]] | |
| − | + | ||
| − | + | ||
| − | + | =Automation section= | |
| − | + | '''Under Construction''' | |
| − | + | [[Category: Quality Assurance]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 09:49, 20 November 2012
Welcome
Welcome to Apache OpenOffice(aka AOO) community. As QA we are helping improve AOO product quality. In generally, we are working on defect handling, manual test, and automation test. If you are interest in QA and willing to make AOO better, don’t hesitate to work with us and contribute your idea and your effort.
QA volunteers please find tasks here:
| Task Type | Task Link | Update Date |
|---|---|---|
| Defect Task | QA/Tasks/DefectTask | Last Update 2012/11/19 |
| Test Case Task | QA/Tasks/TestcaseTask | Last Update 2012/11/20 |
| Automation Scripts Task | *placeholder* |
Following reference for QA tasks
Contents
Working with defect
Confirm “UNCONFIRMED" defect
- Reading defect description carefully to get understand essential of the problem.
- Based on the information provided verify whether the issue can be reproduced against latest build on all supported OS( the purpose of doing that is make sure whether the problem is OS independent).
- Identify regression. Try the defect against some old builds, e.g. released milestone build, to verify if the problem can also be reproduced too. If no, that means the issue is introduced after that build. This will help developer to locate how the defect is introduced.
- Do problem determination (PD). After reproduce defect, analysis defect symptom and function implementation try to give suggestion from QA/end user perspective.
- If the problem can be reproduced, change defect status to “CONFIRMED”, otherwise communicate with reporter to figure out the reproduce steps.
Verify “RESOLVED” defect
- Get latest build which include the fix.
- Follow the reproduce steps on the OS which issue has been reported on, verify if the defect is able to be reproduced or not.
- If the defect cannot be reproduce, then update your verification result to defect’s comments.
- Based on your knowledge to identify which function area may be impacted by this bug fix to do impact testing.
- If no problem found in impact testing, update your test result to defect’s comments. Otherwise reject the defect or accept this fix and open another new defect for the issue just found.
- With all verify/test is passed, change defect status to “VERIFIED” and then change it to “CLOSED”
Open new defect
- When encounter problem while testing product functionality, e.g. running test case, or verifying defect, following this guide to fire bug QA/HowToFileIssue
Working with manual testing
In AOO project, all manual testing assets, e.g. test case, test execution are store in Testlink system(http://aootesting.adfinis-sygroup.org/index.php) , with this system we can
- Perform test case manually.
- Write functionality test case
For Testlink system usage guide, please refer to QA/Testlink
For how to write test case, please refer to QA/Testcase/How_to_write_test_case and sample test case QA/Testcase/Sample
Automation section
Under Construction
