Category:Verify a Bug (Pathway)

(Difference between revisions)
Jump to: navigation, search
(→Pathway Steps, Outcomes, & Learning Activities)
(→Pathway Steps, Outcomes, & Learning Activities)
Line 30: Line 30:
 
{| {{Pathway Step Table}}
 
{| {{Pathway Step Table}}
 
|-
 
|-
−
| 1. Read the bug report on the issue tracker.
+
| 1. Select a bug.
 +
|
 +
* [[:Category:Information Processing|Info Proc]]
 +
|
 +
[[Bug Selection]]
 +
|-
 +
| 2. Read the bug report on the issue tracker.
 
: i. If there is enough information to reproduce the bug continue to step 2.  
 
: i. If there is enough information to reproduce the bug continue to step 2.  
 
: ii. Otherwise, use the issue tracker to ask the reporter for more information.
 
: ii. Otherwise, use the issue tracker to ask the reporter for more information.
Line 41: Line 47:
 
[[Bug Selection]]
 
[[Bug Selection]]
 
|-
 
|-
−
| 2. Reproduce the bug
+
| 3. Reproduce the bug
 
: i. Run the program
 
: i. Run the program
 
: ii. Follow the steps outlined in the bug report. If the steps cannot be followed, use the issue tracker to ask the reporter for clarification.
 
: ii. Follow the steps outlined in the bug report. If the steps cannot be followed, use the issue tracker to ask the reporter for clarification.
Line 54: Line 60:
 
[[Reproduce a Bug Activity]]
 
[[Reproduce a Bug Activity]]
 
|-
 
|-
−
| 3. Report results on the issue tracker
+
| 4. Report results on the issue tracker
 
| Report posted to issue tracker.
 
| Report posted to issue tracker.
 
|  
 
|  

Revision as of 00:14, 9 March 2017


The contributor will: study and attempt to reproduce a bug in the issue tracker, and update the issue to indicate that the bug was verified or that more information is needed. The contribution is: more information about the bug, which could make it easier to fix.

Prerequisites

Area The contributor must be able to:
Software Configuration
  • Download and install the development environment.
  • Run the program.
Issue Tracker
  • Describe issue trackers and how they are used.
  • Access the issue tracker with appropriate permissions.
  • Read, create, and update issues in a tracker.
Community
  • Describe the community guidelines for bug management and triage.

Pathway Steps, Outcomes, & Learning Activities

Follow the project’s policies and practices to complete the steps below.

Pathway Step Step Outcome Process Skills Focus Related Learning Activities
1. Select a bug.

Bug Selection

2. Read the bug report on the issue tracker.
i. If there is enough information to reproduce the bug continue to step 2.
ii. Otherwise, use the issue tracker to ask the reporter for more information.
Exception: Couldn’t understand the report: ask the reporter for additional information using the issue tracker
Decision to proceed to the next step or a request for more information in the issue tracker.

Bug Selection

3. Reproduce the bug
i. Run the program
ii. Follow the steps outlined in the bug report. If the steps cannot be followed, use the issue tracker to ask the reporter for clarification.
Exception: Procedure in bug report could not be followed: ask reporter for clarification using the issue tracker
iii. Observe the program’s behavior
Observation of program behavior or a request for more information in the issue tracker.

Reproduce a Bug Activity

4. Report results on the issue tracker Report posted to issue tracker.

Part of Reproduce a Bug Activity

Notes for Learning Activities Related to this Pathway

When creating activities:

  1. Use examples to demonstrate concepts to student.
  2. Use screen shots when possible.
  3. Prompt students to indicate the exact steps taken to replicate the bug.

Pages in category "Verify a Bug (Pathway)"

This category contains only the following page.

B

Retrieved from "http://foss2serve.org/index.php?title=Category:Verify_a_Bug_(Pathway)&oldid=9722"
Personal tools
Namespaces
Variants
Actions
Events
Learning Resources
HFOSS Projects
Evaluation
Navigation
Toolbox