Changes between Version 23 and Version 24 of BugReportingGuidelines

Timestamp:

02/02/10 20:27:55 (15 years ago)

Author:

Chamindra de Silva

Comment:

--

BugReportingGuidelines

@@ -21 +21 @@
 
 ''Testing UAT''
+
+UAT is a static version for testing before it gets uploaded to production. Please do the majority of your testing here
+
  1. Select an area that you will test in TestCases and add your name to it. Pick a module that has not been covered by others.
  1. Test the UAT version http://haiti-test.sahanafoundation.org by exploring the various navigation options and actions in the module
@@ -27 +30 @@
    * if the bug exists in production mark the version of the bug as haiti-prod 
    * if the bug does not exist in production mark the version as haiti-uat 
+ 1. Check if the bug already exists in the bug tracker by searching for tickets http://trac.sahanapy.org/search or looking at report #9 http://trac.sahanapy.org/report
  1. Use the template below to enter the new bug in trac: http://trac.sahanapy.org/newticket
+
+''Testing Prod''
 
 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 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
+''Testing Dev''
+ * The Dev environment is updated quite regularly, so don't be surprised to see some effects (RMS especially is changing rapidly)
+ * The Dev environment has modules activated which are not in production, so log these bugs as Low priority for now: DVI, Vol
 
 2 Trackers being used: