Changes between Version 1 and Version 2 of BugReportingGuidelines


Ignore:
Timestamp:
01/19/10 11:50:55 (12 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BugReportingGuidelines

    v1 v2  
    11== Bug Reporting Guidelines ==
    22
    3 Screenshots are good.
    4 However, if you get a ticket, then simply the ticket ID would be better than a screenshot, as quicker to access text
     3For now we are only taking bugs on the Haiti Portal:
     4 * http://haiti.sahanafoundation.org/
     5
     6If you are doing system testing rather than just encountering a bug during data entry, then please test on the Dev environment:
     7 * http://haiti-orgsdev.sahanafoundation.org/
     8
     92 Trackers being used:
     10 * [https://bugs.launchpad.net/sahana LaunchPad] - quicker for Devs, but login required to report
     11 * [http://trac.sahanapy.org/query?status=accepted&status=assigned&status=new&status=reopened&col=id&col=summary&col=status&col=owner&col=type&col=component&col=resolution&col=reporter&group=priority&order=priority&version=haiti-pydev&report=9 Trac] - easier for users (anonymous people can report bugs)
     12
     13
     14Please provide full details to reproduce the problem, like the example below.
     15
     16Be clear on whether your test is against the Live system (Prod) or the test system (Dev).
     17
     18Screenshots 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 quicker to access text
    519
    620Example:
    721{{{
    8 Environment/Configurations:
     22System Tested:
     23Dev
    924
    10 Firefox browser – version 3.5
    11 Internet Explorer - version 7.0.5730.13
    12 OS Name - Microsoft Windows XP Professional
    13 Version - 2002 Service Pack 3
     25Browser:
     26Firefox 3.5
     27Windows XP
    1428
    15 Steps to reproduce:
     29Prerequisites:
     30User should be logged in to the system.
    1631
    17 1. Go to above mentioned link and log in as an admin.
    18 
    19     Username:  chamindra@opensource.lk
    20     Password: tester
    21 
    22 2. Now you are in Home page
    23 3. Click on Activities Report
     32Steps:
     331) Click ‘Mapping’.
     342) Click ‘Map Service Catalogue’.
     353) Click ‘Features’.
     364) Click on an ID in the Location list. (The 'Edit location' page will appear.)
     376) Remove the value in the 'Latitude' field. (This step is optional)
     385) Click on 'Conversion Tool' link.
    2439
    2540Expected Result:
    2641
    27 Activities Report page must be loaded.
     42    The Converter should appear.
    2843
    2944Actual Result:
    3045
    31 User does not get an appropriate page. A page loads with a message "Internal Error" and shows a link to where the ticket issued. But that link is also not working. It loads with a page “Forbidden”.
    32 
    33 Screen shot:
    34 
    35 I’ve attached a snap shot of the situation.
    36 
    37    1. First snap shot has taken in Firefox browser when the user clicks on the link.
    38    2. Second shot shows what user gets after clicks on the Ticket Issued.
    39    3. Third snap shot has taken in IE browser when the user clicks on the link.
    40    4. Forth snap shot shows what user gets after clicks on the Ticket Issued.
     46    Clicking the link results nothing. Converter doesn't appear.
    4147}}}
    4248---