Research Bug Activity

From Foss2Serve
(Difference between revisions)
Jump to: navigation, search
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
== Research Bug Activity ==
+
__NOTOC__
  
−
=== Preparation: ===
+
{{Learning Activity Overview
 +
|title=
 +
Research Bug Activity
 +
|overview=  
 +
Learners will choose a fixed defect or feature, research its history, and summarize in an online format. 
 +
|prerequisites=
 +
Basic understanding of what a bug/enhancement is.
 +
|objectives=
 +
# Understand the source of a bug. 
 +
# Trace the history of a bug.
 +
# Articulate how and why a bug was resolved.
 +
|process skills=
 +
}}
  
−
{| border="1"
+
=== Background ===
−
|-
+
−
|'''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. Related activities: [[Bug_Tracker_Activity | Bug Tracker Activity]]
+
−
|-
+
−
|'''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: ===
 
 
Read this [http://en.wikibooks.org/wiki/Introduction_to_Software_Engineering/Tools/Bug_tracking_system|| Introduction to Bug Tracking Systems]
 
Read this [http://en.wikibooks.org/wiki/Introduction_to_Software_Engineering/Tools/Bug_tracking_system|| Introduction to Bug Tracking Systems]
  
−
=== Directions: ===
+
=== Directions ===
 +
 
 
# Go to the Gnome bugzilla instance: https://bugzilla.gnome.org/
 
# Go to the Gnome bugzilla instance: https://bugzilla.gnome.org/
 
# Find the MouseTrap closed bugs:
 
# Find the MouseTrap closed bugs:
Line 42: Line 37:
 
# Report your findings in a blog post. Turn in a link to your blog post.  
 
# Report your findings in a blog post. Turn in a link to your blog post.  
  
−
--------------------
 
−
This work is licensed under a
 
−
[http://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International License]
 
  
−
[[File:CC_license.png]]
+
=== Deliverables ===
 +
 
 +
Provide a link to your blog post.
 +
 
 +
=== Assessment ===
 +
 
 +
=== Comments ===
 +
 
 +
Related activities: [[Intro to Bug Trackers (Activity)]]
 +
 
 +
{{Learning Activity Info
 +
|acm unit=
 +
|acm topic=
 +
Testing
 +
|difficulty=
 +
Easy
 +
|time=
 +
60 minutes
 +
|environment=
 +
Access to Internet/Web and web browser.
 +
|author=
 +
Heidi Ellis
 +
|source=
 +
|license=
 +
{{License CC BY SA}}
 +
}}
 +
 
 +
=== Suggestions for the Open Source Project ===
 +
 
 +
MouseTrap or other GNOME project.
 +
 
  
−
[[Category: Learning_Activity]]
+
[[Category:Learning Activity]]
−
[[Category:Quality_And_Testing]]
+
[[Category:Communication and Tools]]
 +
[[Category:Bugzilla]]
 +
[[Category:Quality and Testing]]
 +
[[Category:CS Principles]]
 +
[[Category:CS1]]
 +
[[Category: Good Draft]]

Latest revision as of 17:53, 8 March 2017


Title

Research Bug Activity

Overview

Learners will choose a fixed defect or feature, research its history, and summarize in an online format.

Prerequisites

Basic understanding of what a bug/enhancement is.

Learning
Objectives 		After successfully completing this activity, the learner should be able to:
  1. Understand the source of a bug.
  2. Trace the history of a bug.
  3. Articulate how and why a bug was resolved.
Process Skills
Practiced


Background

Read this Introduction to Bug Tracking Systems

Directions

  1. Go to the Gnome bugzilla instance: https://bugzilla.gnome.org/
  2. Find the MouseTrap closed bugs:
    1. From the main Gnome Bugzilla page, click on the Search icon
    2. Under Status select Closed
    3. Under Product select mousetrap (hint: repeatedly press 'm' until you tab down to mousetrap)
    4. In the Words slot enter 'fix'
  3. You should now see a list of closed bugs. Select a defect or feature from this list
  4. Read the bug report and history carefully to determine:
    1. When was the bug reported?
    2. Who reported the bug?
    3. What actions were taken on the bug and by whom?
    4. When was the bug fixed?
    5. What was the fix?
    6. Who made the fix.
  5. Report your findings in a blog post. Turn in a link to your blog post.


Deliverables

Provide a link to your blog post.

Assessment

Comments

Related activities: Intro to Bug Trackers (Activity)

ACM BoK
Area & Unit(s)
ACM BoK
Topic(s)

Testing

Difficulty

Easy

Estimated Time
to Complete

60 minutes

Environment /
Materials

Access to Internet/Web and web browser.

Author(s)

Heidi Ellis

Source
License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License

CC license.png


Suggestions for the Open Source Project

MouseTrap or other GNOME project.

Retrieved from "http://foss2serve.org/index.php?title=Research_Bug_Activity&oldid=9514"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox