Changes between Version 30 and Version 31 of BugReportingGuidelines


Ignore:
Timestamp:
07/04/10 10:42:17 (11 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReportingGuidelines

    v30 v31  
    55
    66When there is a production instance running, progression of code is normally from Dev -> UAT -> Prod
    7 
    8 === High Priority Focuses for testing ===
    9 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].
    10 
    11 === Testing Coverage ===
    12 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
    13  * TestCases page is the main page where all testers work off from and handle assignments and coverage
    14  * UAT is a static version for testing before it gets uploaded to production. Please do the majority of your testing here
    15  * The Dev environment is updated quite regularly, so don't be surprised to see some effects
    16  * The Dev environment has modules activated which are not in Production, so log these bugs as Low priority for now: DVI, Vol
    177
    188=== Tips ===
     
    6050    Clicking the link results nothing. Converter doesn't appear.
    6151}}}
     52
     53=== High Priority Focuses for testing ===
     54Production 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].
     55
     56=== Testing Coverage ===
     57It 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
     58 * TestCases page is the main page where all testers work off from and handle assignments and coverage
     59 * UAT is a static version for testing before it gets uploaded to production. Please do the majority of your testing here
     60 * The Dev environment is updated quite regularly, so don't be surprised to see some effects
     61 * The Dev environment has modules activated which are not in Production, so log these bugs as Low priority for now: DVI, Vol
     62