Miro Testing

So you’ve found a bug, or maybe you have an enhancement request.  You’ve taken the time to fill out the form, provide useful detailed information, log files… click Submit.  You check your email the next day and find that all your work has been returned with the simple statement:  Duplicate.

Arrgh.

You can avoid all that with a few simple search tips - which will save yourself some effort and help us track and reproduce existing bugs.

If you are running the regression test cases and you encounter what you think is a bug, the easiest way to look for a duplicate is to first check those that are associated with the test case.  Along the right side of each test case title, there is a view button.

Clicking that button will open a table containing the history of that particular test case and contain links to any bugs reported.  Clicking on the comment will display brief information the tester entered about the error.  Selecting the link in the right column will open the bug in bugzilla.

If you use firefox for your browser, then the searching is super easy once you add bugzilla to your list of search engines.  Go to the PCF instance of bugzilla.  Then, right-click in the search engine pulldown list and select Add Bugzilla.  After that - you can select bugzilla as your engine, enter some descriptive words and it will perform a quick search of only open bugs.   Usually a quick browsing this list of bugs and enhancement requests is all it takes to find the duplicate.

And lastly, what about when you get an automatic crash reporter notification that look like this:

For the 2.0 release, we have added a new diagnostics tool.  From the Miro Help menu, select Diagnostics.  This will open a window that displays essential information about Miro on your system.  Click the Show button for the Log file location.

If you browse through the log file, you will see some the exception information.  A crash report always starts with  —– CRASH REPORT (DANGER CAN HAPPEN) —–, after that we provide revision and system information.  Below that is the Exception information:

If you copy some of the unique words from the last line of the exception information, and drop it in the bugzilla search - you should be able to tell if that particular crash has been reported.  Reporting those crashes with log information is an extra step you can take that is very helpful.

What to do if your bug is already in bugzilla?  Please, add a comment to the bug with your operating system, build information and any extra information that can help the developers reproduce it.