Changes between Version 27 and Version 28 of BugReportingGuidelines


Ignore:
Timestamp:
05/29/10 14:12:23 (12 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReportingGuidelines

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