Changes between Version 21 and Version 22 of BugReportingGuidelines

Timestamp:

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

Author:

Chamindra de Silva

Comment:

--

BugReportingGuidelines

@@ -11 +11 @@
 
 '''High Priority Focuses for testing'''
- * Testing on the selection of markers in the Mapping module on dev
- * Testing of hospitals on UAT
- * [DeveloperGuidelinesUsability Usability Testing]
+ * Issues on live Production system
+ * Issues with Hospital and Request systems 
 
 '''Testing Coverage'''
-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. We are currently testing ''UAT version'': r619 (2010-01-29 08:33:52) .
-
-The TestCases Page helps you with test coverage. Please select an area for testing and add yourself to the page:
+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
  * TestCases
 
-'''Rules of Engagement'''
+'''Test Process'''
+
+''Testing UAT''
+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
+1. Add you initials to the respective test case in TestCases. If the action does not exist in the TestCases please add it as well.
+1. If you find a bug also check if this bug exists in the production version http://haiti.sahanafoundation.org
+   * 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. Use the template below to enter the new bug in trac: http://trac.sahanapy.org/newticket
 
 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]