Research Bug Activity
(Difference between revisions)
Heidi.ellis (Talk | contribs)
(Created page with "== Research Bug Activity == === Preparation: === {| border="1" |- |'''Description''' ||Learners will choose a fixed defect or feature, research its history, and summarize i...")
Newer edit →
(Created page with "== Research Bug Activity == === Preparation: === {| border="1" |- |'''Description''' ||Learners will choose a fixed defect or feature, research its history, and summarize i...")
Newer edit →
Revision as of 18:22, 26 May 2015
Contents |
Research Bug Activity
Preparation:
Description | Learners will choose a fixed defect or feature, research its history, and summarize in an online format. |
Source | 50 Ways |
Prerequisite Knowledge | Basic understanding of what a bug/enhancement is. |
Estimated Time to Completion | 60 minutes |
Learning Objectives | To understand the source of a bug. To trace the history of a bug. To be able to articulate how and why a bug was resolved. |
Materials/Environment | Access to Internet/Web and web browser. |
Rights | Licensed CC BY-SA |
Turn In | A link to your blog post. |
Background:
Directions:
- Go to the Gnome bugzilla instance: https://bugzilla.gnome.org/
- Find the MouseTrap closed bugs:
- From the main Gnome Bugzilla page, click on the Search icon
- Under Status select Closed
- Under Product select mousetrap (hint: repeatedly press 'm' until you tab down to mousetrap)
- In the Words slot enter 'fix'
- You should now see a list of closed bugs. Select a defect or feature from this list
- Read the bug report and history carefully to determine:
- When was the bug reported?
- Who reported the bug?
- What actions were taken on the bug and by whom?
- When was the bug fixed?
- What was the fix?
- Who made the fix.
- Report your findings in a blog post. Turn in a link to your blog post.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License