Changes between Version 28 and Version 29 of BugReportingGuidelines
- Timestamp:
- 05/29/10 14:14:10 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BugReportingGuidelines
v28 v29 2 2 == Bug Reporting Guidelines == 3 3 4 Currently we are mainly taking bugs on: 5 * '''Demo''' (Development): http://demo.eden.sahanafoundation.org 4 6 5 For now we are only taking bugs on: 6 * '''Demo''' (User Acceptance): http://demo.eden.sahanafoundation.org 7 When there is a production instance running, progression of code is normally from Dev -> UAT -> Prod 7 8 8 Progression of code will normally be from Dev -> UAT -> Prod 9 10 '''High Priority Focuses for testing''' 11 * Issues on live Production systems 12 13 '''Testing Coverage''' 9 === High Priority Focuses for testing === 14 10 Production testing is done as a result of doing Data Entry - this is usually the critical path as we're always short on data & this is the area which needs to be made more bullet-proof & smooth. Data Entry tasks are coordinated using a Google Spreadsheet, like [http://spreadsheets.google.com/ccc?key=0Aq_3OYelM4ZUdHJyc0lUekZLUmEwa3ZSU2dJS3YyWWc&hl=en_GB this one used for Haiti]. 15 11 12 === Testing Coverage === 16 13 It would be good if the QA team specializes on testing certain modules in the system. More than one person can subscribe for a module and report their test coverage. The TestCases Page helps you with test coverage. Please select an area for testing and add yourself to the page 17 14 * TestCases page is the main page where all testers work off from and handle assignments and coverage … … 20 17 * The Dev environment has modules activated which are not in Production, so log these bugs as Low priority for now: DVI, Vol 21 18 22 23 '''Tips''' 19 === Tips === 24 20 * Please check the trackers to see if the bug you are reporting has already been reported ([https://bugs.launchpad.net/sahana LaunchPad] provides a nice interface for this) 25 21 * Please provide full details to reproduce the problem, like the example below. … … 28 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 can simply copy/paste to find the relevant ticket) 29 25 30 '''Bug Priorities''' 26 === Bug Priorities === 31 27 * Critical - big functionality, stability and data integrity defects in a Production instance 32 28 * Major - functionality and data integrity defects in UAT only … … 34 30 * Trivial - Data validation defects, Domain defects 35 31 36 Example: 32 === Example === 37 33 {{{ 38 34 System Tested:
