Meego Wiki
Views

Quality/Bugtriage Tasks

From MeeGo wiki
< Quality
Revision as of 19:55, 22 October 2010 by Andre (Talk | contribs)
Jump to: navigation, search

There are a number of ways to start triaging. If you have more ideas feel free to add them here.

Contents

Triage a single application

Pick up the product or component that interest you, or which you know about, or are willing to learn, or happen to use. You can query for existing open reports and take a look at issues that interest you, for example in order to update them by updating the Version field, or noting that they have been already fixed in the version you use (please mention the exact version that you use in a comment). If you want to constantly be informed about any changes, set up user watching by adding the "Default QA Contact" email address to your "User Watching" list. See this blogpost for bugs.maemo.org for a longer explanation about how this works.

Triage the latest incoming reports

Take a look at the latest incoming reports of the last two weeks (NEW and REOPENED state) and try to reproduce them, or ask for missing information, or add additional information. See the Triage Guide.

Try to reproduce reports

Many reported problems cannot be easily reproduced. Take a look at bug reports in NEW state, try to reproduce them, and feel free to add a comment either with instructions to reproduce or that you could not reproduce it and mention the version that you use.

Update reports of older versions

TO DO: Is this information accurate and correct? -- User:Andre

Query for bug reports with an old MeeGo Release (Version) number and try to reproduce them with the latest software release to find out whether the reports are still valid. If they have been fixed in the meantime, you can add a comment about it.

Clean up reports that need more information

TO DO: Add link to Stock answers in case we introduce them, and add a "Update the stock answers" section here. -- User:Andre

Clean up bugs in NEEDINFO state that have not been changed for 6 months. This means that more information had been requested from the reporter but has not been provided. These bugs should be closed as WORKSFORME if you are not able to reproduce. If there is simply not enough information to be a useful report, then close the bug as INVALID. Please always explain your decision by adding a nice comment and in the latter case, ask the reporter to provide the information asked for, if he can, and reopen the bug.

Update your own reports

Most of us have submitted bugs in the past and forgotten about them. Take a look at them and check whether they still apply in the latest software version. Go to the Query website and make sure that under "Status" NEW, ASSIGNED and REOPENED are checked. Under "Email and Numbering", check the field "the reporter" and enter your email address below in the text field to query for them.

Personal tools