Changes between Version 38 and Version 39 of BugReportingGuidelines

07/25/10 22:03:45 (14 years ago)
Fran Boon



  • BugReportingGuidelines

    v38 v39  
    1414 * Bug Supervisors may wish to check the [ Commit Logs] to see if they can see the Bug being fixed.
    1515 * '''Screenshots''' are good for showing the main problem screen if hard to explain, however, if you get a ticket, then simply the ticket ID would be better than a screenshot, as can simply copy/paste to find the relevant ticket)
    1617=== Bug Priorities ===
    1718 * Critical - big functionality, stability and data integrity defects in a Production instance
    5253    Clicking the link results nothing. Converter doesn't appear.
    55 === High Priority Focuses for testing ===
    56 Production testing is done as a result of doing Data Entry - this is usually the critical path as we're generally short on data & this is the area which needs to be made more bullet-proof & smooth. Data Entry tasks can be coordinated using a Google Spreadsheet, like [ this one used for Haiti].
    58 === Testing Coverage ===
    59 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
    60  * TestCases page is the main page where all testers work off from and handle assignments and coverage
    61  * UAT is a static version for testing before it gets uploaded to production. Please do the majority of your testing here
    62  * The Dev environment is updated quite regularly, so don't be surprised to see some effects
    63  * The Dev environment has modules activated which are not in Production, so log these bugs as Low priority for now: DVI, Vol