Category:Verify a Bug (Pathway)
From Foss2Serve
(Difference between revisions)
Lori.postner (Talk | contribs) (→Pathway Steps, Outcomes, & Learning Activities) |
Lori.postner (Talk | contribs) (→Pathway Steps, Outcomes, & Learning Activities) |
||
(15 intermediate revisions by one user not shown) | |||
Line 18: | Line 18: | ||
* Access the issue tracker with appropriate permissions. | * Access the issue tracker with appropriate permissions. | ||
* Read, create, and update issues in a tracker. | * Read, create, and update issues in a tracker. | ||
+ | * Complete the [[Research Bug Activity]] or [[Intro to Bug Trackers (Activity)]] | ||
|- | |- | ||
| Community | | Community | ||
Line 30: | Line 31: | ||
{| {{Pathway Step Table}} | {| {{Pathway Step Table}} | ||
|- | |- | ||
− | | 1. Read the bug report on the issue tracker. | + | | 1. Select a bug. |
+ | | Bug identified | ||
+ | | | ||
+ | * [[:Category:Information Processing|Info Proc]] | ||
+ | | | ||
+ | [[Bug Selection]] | ||
+ | |||
+ | [[Solving A Bug]] (incorrectly named) | ||
+ | |- | ||
+ | | 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 39: | Line 49: | ||
* [[:Category:Written Communication|Writ Comm]] | * [[:Category:Written Communication|Writ Comm]] | ||
| | | | ||
− | [[Bug | + | [[Bug Gardening]] |
+ | |||
+ | [[Write a Bug Report (Activity)]] | ||
|- | |- | ||
− | | | + | | 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 66: | ||
[[Reproduce a Bug Activity]] | [[Reproduce a Bug Activity]] | ||
|- | |- | ||
− | | | + | | 4. Report results on the issue tracker |
| Report posted to issue tracker. | | Report posted to issue tracker. | ||
| | | |
Latest revision as of 00:40, 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 |
|
Issue Tracker |
|
Community |
|
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 identified |
Solving A Bug (incorrectly named) | |
2. Read the bug report on the issue tracker.
|
Decision to proceed to the next step or a request for more information in the issue tracker. | ||
3. Reproduce the bug
|
Observation of program behavior or a request for more information in the issue tracker. | ||
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:
- Use examples to demonstrate concepts to student.
- Use screen shots when possible.
- 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.