Post by Choclate on Apr 28, 2010 0:36:55 GMT -5
HOW TO:: Submit a Bug Report
Finding bugs is a good thing! It helps with making Chocoparse as good of a parser as it can be. What isn't good is bug reports that are cryptic. Here is a helpful guide on submitting a detailed and helpful bug report.
If you encounter an error that you think is a bug, try to make it happen more than once. A bug that is difficult to reproduce is difficult to report and even more difficult to resolve.
Be sure to include:
Version Information
What version of Chocoparse are you using? Running Chocoparse with no arguments will output version information.
Concise but detailed description of the bug.
What happened? Were there any error messages, what is the exact text of the error messages?
Steps to Reproduce
A detailed list of steps to re-produce the bug you encountered.
Attachments, if applicable
Look at chocoparse.log, it will have error messages logged to it! If you feel a screenshot is helpful, add one!
Finding bugs is a good thing! It helps with making Chocoparse as good of a parser as it can be. What isn't good is bug reports that are cryptic. Here is a helpful guide on submitting a detailed and helpful bug report.
If you encounter an error that you think is a bug, try to make it happen more than once. A bug that is difficult to reproduce is difficult to report and even more difficult to resolve.
Be sure to include:
Version Information
What version of Chocoparse are you using? Running Chocoparse with no arguments will output version information.
Concise but detailed description of the bug.
What happened? Were there any error messages, what is the exact text of the error messages?
Steps to Reproduce
A detailed list of steps to re-produce the bug you encountered.
Attachments, if applicable
Look at chocoparse.log, it will have error messages logged to it! If you feel a screenshot is helpful, add one!