Changes between Version 10 and Version 11 of BugReportingGuidelines

Timestamp:

01/26/10 12:32:33 (15 years ago)

Author:

Chamindra de Silva

Comment:

--

BugReportingGuidelines

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