Miro Quality Assurance
From Team Miro Wiki
As a cross-platform application that gets translated into a number of foreign languages, Miro has a lot of places where bugs can hide.
We are constantly improving Miro - adding the features that you want and fixing the bugs that slipped out. Sometimes these changes have unfortunate side effects, and break existing functionality. Testing early and often helps ensure that these errors are found and fixed.
With so many users - we often get duplicate submissions or reports that are not very specific. We need to eliminate duplicates and clean up the bug reports to make it faster and easier for the developers to resolve them.
We have been small group for a long time, and these tasks are fairly large for a just a few people to accomplish - however they can easily be shared among many people.
Giving us a little of your time will give back a lot to our community.
Contents |
Who can help?
You don't have to be a software developer or a video creator to help improve Miro. We rely on a number of users to help verify build quality, file bugs, and run tests.
Our view of what makes a good tester is posted on the Miro Testing blog.
How you can help?
There are many ways to help us and each is as valuable as the other.
New Feature Testing
1. Subscribe to the Miro Testing blog. Each week it highlights the changes to the baseline. 2. Download the recommended testing build. 3. Run through test cases described in the weekly testing wiki. 4. Edit the wiki page to include any additional tests you think are missing. 5. Report any bugs that you find.
Regression Testing
1. Download the latest nightly build or revision build. 2. Go to Miro Regression tests and run either the Quicktest or other recommended test run. 3. Report any bugs that you find.
Bug Reporting and Reproduction
1 Problems are reported in many places. 2. Watch for reports in the bugzilla timeline, the forum, or in the chatroom. 3. See if you can reproduce the problem. 4. Update the bug report (or create a new ones) to contain clear steps.
Bugzilla Cleanup
1. The bug database contains a large number of tickets, many of them are Democracy leftovers. 2. Open a ticket and see if you can reproduce the error described. 3. If the functionality is not working, add your test steps. 4. If the bug is no longer valid, add your steps and close the tickets as worksforme.
Where do I sign up?
1. Sign up for the Miro Testers mailing list 2. Subscribe to the Miro Testing blog. 3. Go to the Regression Testing site and create an account.
Test Talks
I like to set up a monthly or so chat time that will work for most people. Email me your opinion. But you can almost find me in the chatroom irc.freenode.org#miro. Look for dragojevic, janet or jed.
QA Resources
GoodBugReports - Information for creating a very useful bug report
Test cases - Test cases covering Miro functionality - useful for advanced users who want to help test
Test support information - useful information for log files, and variables that can be set.
System Information - way to find the tech specs of your system for bug reporting
Log File Guide - quick help for reading the log file to search for duplicate tickets.
Keyboard Shortcuts - defines the implemented keyboard shortcuts - should be used as the reference when testing that functionality.
Playback Formats - link to Miro FAQ about supported formats for video / audio playback.
Mailing list - Sign up for the Miro testing mailing list.
Litmus - Miro testcase management tool.
Contact
For any specific questions, just email - jed [at] pculture [dot] org
