How to Test, Report, and Ticket (in detail)

Background

GeoMOOSE uses Trac to keep track of documentation, tasks, bugs, enhancements, and most other details of the project. Trac is also the system for feedback about testing, particularlly around a release. See also general faq How_should_I_report_a_bug?

Where to test?

Testing should be done on the stable demo or trunk demo depending on which you are reporting on. Another publically accesible instance can also be used if the demo is not configured with that specfic functionality.

What to test?

Generally try to give the site a thorough check of the main functionality (search, identify, print, zoom, measure, layer tools, select) and specifically the issue that concerns you. This helps find any issues that may have been introduced as part of the change for your issue of concern.

Oops, there is an error. How to report this?

1. See also general faq How_should_I_report_a_bug?
2. Login to Trac which requires an OSGeo userid
3. Open a ticket
4. Document your browser(s) and GeoMOOSE version
5. Document the steps you could use to replicate the error
6. Document the error behavior
7. Make an effort to assign the correct Component, Type, Priority, Version, and useful keywords. For things you don’t know, a guess or the default are ok. The Type for bugs is ‘defect’

That works, but... How to request an enhancement?

1. See also, general faq How_should_I_request_an_enhancement?
2. Login to Trac which requires an OSGeo userid
3. Open a ticket
4. Identify start state
5. Document behavior your enhancement needs to do
6. Document end state
7. Make an effort to assign the correct Component, Type, Priority, Version, and useful keywords. For things you don’t know, a guess or the default are ok. The Type for enhancements is ‘enhancement’
8. Consider providing a patch, funding, testing, documentation or other efforts to make this a more likely enhancement

What happens now that there is a ticket?

1. Developer will ascertain that the work needs to be completed. If not the developer will add to notes
2. Developer will work and mark assigned status to “accepted”
3. Developer will document and comment on the programming completed
4. Developer will change status to “testing”
5. Trunk demo version will be updated

How do I follow up?

1. Pay attention and respond promptly when you get notification of activity on the ticket
2. Follow the steps identified in the original ticket to replicate the problem this time testing on the trunk demo
3. If problem has been addressed

1. Enter what steps you did to verify the problem has been addressed
2. Identify what browser and version of GeoMoose you tested this on (if relevant)
3. Resolve problem as “fixed” in status

4. If problem still exists or causes additional problems

1. Enter what steps you did to that still causes problem
2. Identify what browser and version of GeoMoose you tested this on (if relevant)
3. Convert action to: “reassign to” programmer that did the work

5. If you find a new problem then start this process again with the new problem.

Note: follow through with your reported tickets

Please note if you open a ticket you are responsible to ensure that when development is completed you will test to ensure that the work addresses the documented problem. When you open a ticket you are also committing to following this operating procedure.