wiki:frp

Bug Reporting Guidelines

Testing Site: http://frp-test.sahanafoundation.org/ Development Site: http://frp-dev.sahanafoundation.org/

Current revision is: frp-0.9.5-603 (2010-02-12 08:53:16) (ref: http://frp-test.sahanafoundation.org/frp/default/about )

Reports

These User roles have been pre-setup so that you can use it to test

  • Admin: frp @ sahanafoundation.org
  • IP User: ip_user, ip_user2, ip_user3, ip_user4 @ sahanafoundation.org,
  • IP Admin: ip_admin @ sahanafoundation.org
  • FAC user: fac_user @ sahanafoundation.org
  • FAC admin: fac_admin @ sahanafoundation.org
  • Translators: translator @ sahanafoundation.org

Common Password: haiti

Steps to Report a Bug

  1. Search the FRP bug report to see if this bug has already been reported (does not have to be a exhaustive search, but a simple skim). Check report http://trac.sahanapy.org/report/14
  2. If not click on New Ticket or goto URL http://trac.sahanapy.org/newticket
  3. Describe the bug using the template and guidelines below and ideally add a screenshot
    • Leave Milestone blank
    • Mark the version as frp-test if it is a bug on the testing site
    • Use the appropriate module name frs, admin, mapping, organization, UI (optional)
  4. Add optional fields
    • Optional: Use Bug Priority scale below and Description template below
    • At the Requirement Number of the URD if it is relevant
    • To attach a screenshot click on I have files to attach to this ticket and upload the file after submitting the first form (a picture is worth a thousand words to explain the issue !)

Bug Priorities (a scale for FRP specifically)

  • Critical - big functionality, stability and data integrity defects
  • Major - Functionality defects, mis-expectations on key requirements
  • Minor - UI, Style, Usability defects
  • Trivial - Minor alignment issues, nice to have

Description Template:

http://frp-test.sahanafoundation.org/frp/default/about

System Tested:
Sahana rel-frp-beta-582

Browser:
Firefox 3.5
Windows XP

Steps:
1) Click ‘Mapping’.
6) Remove the value in the 'Latitude' field. (This step is optional)
5) Click on 'Conversion Tool' link.

Expected Result:

    The Converter should appear.

Actual Result:

    Clicking the link results nothing. Converter doesn't appear.

UAT site update process

  1. Dominic notifies frp@sahanafoundation.org of new version available for update with change log preferably and if the database needs to be flushed 2, Chamindra notifies Julien of pending update on UAT (Test) site though IRC/email/skype
  2. Julien confirms update of testing site to Chamindra through IRC/email/skype
  3. Chamindra or Praneeth updates the UAT site and logins as specified in trac
  4. Chamindra updates trac with all new details
  5. Update email is sent to frp team and julien / john-paul
Last modified 15 years ago Last modified on 02/15/10 04:35:36
Note: See TracWiki for help on using the wiki.