Changes between Version 5 and Version 6 of BugReportingGuidelines
- Timestamp:
- 01/19/10 16:39:02 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BugReportingGuidelines
v5 v6 6 6 * http://haiti.sahanafoundation.org/ 7 7 8 Ideally this testing is done as a result of doing Data Entry - this is the critical path right now as we're still short on data & this is the area which needs to be made more bullet-proof & smooth. Data Entry tasks are being coordinated using this [http://spreadsheets.google.com/ccc?key=0Aq_3OYelM4ZUdHJyc0lUekZLUmEwa3ZSU2dJS3YyWWc&hl=en_GB Google Spreadsheet] 9 8 10 If you are doing system testing rather than just encountering a bug during data entry, then please test on the Dev environment: 9 11 * http://haiti-orgsdev.sahanafoundation.org/ 10 * NB The Dev environment is updated quite regularly, so don't be surprised to see some effects 11 * NB The Dev environment has modules activated which are not in production, so log these bugs as Low priority for now: 12 * DVI 13 * Vol 12 * NB The Dev environment is updated quite regularly, so don't be surprised to see some effects (RMS especially is changing rapidly) 13 * NB The Dev environment has modules activated which are not in production, so log these bugs as Low priority for now: DVI, Vol 14 14 15 15 2 Trackers being used: … … 17 17 * [http://trac.sahanapy.org/query?status=accepted&status=assigned&status=new&status=reopened&col=id&col=summary&col=status&col=owner&col=type&col=component&col=resolution&col=reporter&group=priority&order=priority&version=haiti-pydev&report=9 Trac] - easier for users (anonymous people can report bugs) 18 18 19 20 19 Please provide full details to reproduce the problem, like the example below. 21 20 22 21 Be clear on whether your test is against the Live system (Prod) or the test system (Dev). 23 22 24 Screenshots are good for showing the main problem screen if hard to explain, however, if you get a ticket, then simply the ticket ID would be better than a screenshot, as quicker to access text23 Screenshots are good for showing the main problem screen if hard to explain, however, if you get a ticket, then simply the ticket ID would be better than a screenshot, as can simply copy/paste to find the relevant ticket) 25 24 26 25 Example: