Category:Verify a Bug (Pathway)
(Difference between revisions)
Lori.postner (Talk | contribs) |
Lori.postner (Talk | contribs) (→Prerequisites) |
||
| 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]] | + | * Complete the [[Research Bug Activity]] or [[Bug Tracker Activity-Mousetrap]] |
|- | |- | ||
| Community | | Community | ||
Revision as of 00:18, 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 | ||
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.
