Changes between Version 10 and Version 11 of BugReportingGuidelines


Ignore:
Timestamp:
01/26/10 12:32:33 (12 years ago)
Author:
Chamindra de Silva
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReportingGuidelines

    v10 v11  
    99Progression of code will normally be from Dev -> UAT -> Prod
    1010
    11 ''Rules of Engagement''
     11'''Rules of Engagement'''
    1212
    1313Ideally 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]
    1414
    15 If you are doing system testing rather than just encountering a bug during data entry, then please test on the Dev environment:
    16  * http://haiti-orgsdev.sahanafoundation.org/
     15If you are doing system testing rather than just encountering a bug during data entry, then please test on the UAT or Dev environment:
     16 * UAT is a static version for testing before it gets uploaded to production. Please do the majority of your testing here
    1717 * NB The Dev environment is updated quite regularly, so don't be surprised to see some effects (RMS especially is changing rapidly)
    1818 * NB The Dev environment has modules activated which are not in production, so log these bugs as Low priority for now: DVI, Vol