105 | | * Look at the [wiki:ProjectInformation#Project:Testing bug testing] project description for the web sites to test (or for installing your own copy if the software, if you'd rather). |
106 | | * Go through the list of [/report/1 open bugs]. Look at reports that have type "defect". Try to reproduce the problem reported in the ticket: |
107 | | * If the issue is gone, add a reply to the ticket with what you did and "resolve" the ticket as "invalid". (The submitter can still reply and reopen the bug if they want.) |
108 | | * If you can reproduce the issue but the description isn't clear, add better "how to reproduce" instructions. |
| 102 | * Register for an account on our [http://demo.eden.sahanafoundation.org/eden/ demo site]. Or you can install your own copy of the software, if you want to test the very latest version. Look at the [wiki:ProjectInformation#Project:Testing bug testing] project description for information on installing.) |
| 103 | * Go through the list of [/report/1 open bugs]. Look at reports that have type "defect". Start with older bugs -- they're more likely to be fixed or no longer relevant. There may be other GCI students working on this, so look for a comment that the bug is being worked on for GCI -- skip those. |
| 104 | * When you've found a bug to look at, add a comment saying you've verifying it for GCI. |
| 105 | * Try to reproduce the problem reported in the ticket: |
| 106 | * If the description of how to make the bug happen is clear, and the bug is gone, add a reply to the ticket with what you did to test it, and "resolve" the ticket as "invalid". (The person who reported the bug can still reply and reopen the bug if they want.) |
| 107 | * If the instructions to cause the bug to happen aren't clear, try to figure out what the reporter meant -- try to find the bug yourself. If you can reproduce the bug, add better "how to reproduce" instructions. See the [wiki:BugReportingGuidelines Bug Reporting Guidelines] for what makes a good bug report. |