Solving A Bug

From Foss2Serve
Revision as of 20:32, 26 May 2015 by Evelyn.Brannock (Talk | contribs)
Jump to: navigation, search


Solving A Bug


Description JUnit is a large, mature free and open source software (FOSS) that is written in Java. Learners will read an open issue in JUnit, find resources to research and understand it, replicate the bug, produce some improved additional test cases while writing a better bug report, and describe the process required to fix the bug.
Source This activity is a specialization of the Solving_A_Bug.
Prerequisite Knowledge 1) Including a library in a Java project 2) Running a JUnit Test Case (No in-depth knowledge of JUnit assumed)
Estimated Time to Completion 120-180 minutes
Learning Objectives Ability to: 1) Understand, investigate and report details on a real, poorly documented, unsolved issue in JUnit a FOSS application, 2) Reproduce a reported bug, 3) Write an improved bug report and 4)Describe the process required to fix the bug.
Materials/Environment Java IDE configured with JUnit 4.12.
Additional Information  ?
Rights Licensed JUnit
Turn In Report that includes screen shots.


Part of your challenge is to find more resources.


Bug tracking systems are a form of change management and organization used by FOSS projects. Bug trackers do far more than simply keep track of bugs. They also are used to hold new feature requests, patches, and some tasks. Bug trackers are also called request trackers, issue trackers and ticket systems.


We will use the GNOME MouseTrap project to explore a typical Bugzilla instance for a project.

Part 1 - Install a version of JUnit

  1. 1. You will download junit-4.12.jar at . Remember the directory location you placed the jar files in.
  2. 2. Create a project in Eclipse.
  3. 3. Add the jUnit-4.12 jar in its build path.

Part 2 - Locate and describe the JUnit Issue

  1. 1. Locate issue number #226 in the github Social Coding JUnit Issue Tracker at
    1. a. How is the issue categorized? Is this a bug or feature request or something else?
    2. b. What date was it reported?
    3. c. Has the issue been assigned?
    4. d. How many participants in the discussion?

Part 3 - Reproduce the JUnit Issue

  1. 1. Using JUnit 4.12, the information supplied about the issue and any other information you may have found in your research answer the following questions:
    1. a. Did the code shown execute?
    2. b. Was your result/output the same as the author of the issue?
    3. c. Take a screen shot of Eclipse when you reproduce the bug, and submit it in your report that answers these questions.

2. In your opinion, was this bug well-written and easy to understand for the first two cases? Why or why not?

Part 2 - Collective Reports

This section refers to the entire GNOME project, not just MouseTrap.

  1. Click on the “Reports” link on the top of the page.
  2. Click on "Summary of bug activity for the last week."
  3. How many bug reports were opened in the last week? How many were closed?
  4. What was the general trend last week? Were more bugs opened than closed or vice versa?
  5. Who were the top three bug closers? Why is this important to know?
  6. Who were the top three bug reporters? Are these the same as the top three bug closes? What is the overlap in these two lists?
  7. Who are the top three contributors of patches?
  8. Who are the top three reviewers of patches? What is the overlap between these lists and the bug closers and bug reporters? What is the overlap between patch contributors and patch reviewers?

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

CC license.png

Personal tools
Learning Resources
HFOSS Projects