Changes between Version 27 and Version 28 of BugReportingGuidelines

Timestamp:

05/29/10 14:12:23 (15 years ago)

Author:

Fran Boon

Comment:

--

BugReportingGuidelines

@@ -12 +12 @@
 
 '''Testing Coverage'''
+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].
+
 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 page is the main page where all testers work off from and handle assignments and coverage
  * UAT is a static version for testing before it gets uploaded to production. Please do the majority of your testing here
- * 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].
  * The Dev environment is updated quite regularly, so don't be surprised to see some effects
  * The Dev environment has modules activated which are not in Production, so log these bugs as Low priority for now: DVI, Vol