Category:Create Unit Tests (Pathway)
(Difference between revisions)
| Line 73: | Line 73: | ||
*[[Examine Branch Test Coverage (Activity)]] | *[[Examine Branch Test Coverage (Activity)]] | ||
*[[Introduction to Static Analysis]] | *[[Introduction to Static Analysis]] | ||
| + | *[[Introduction to Test Driven Development]] | ||
|- | |- | ||
| | | | ||
Revision as of 19:23, 8 March 2017
The contributor will: create unit tests for a software module (class, file, etc).
The contribution is: unit tests accepted into the project's codebase, and test results logged on issue tracker or otherwise accepted by the community.
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. Download and install the project |
Project is installed | ||
|
2. Run the project |
Project is run | ||
|
3. Work with community (or check issue tracker?) to find module that needs unit tests |
Module that needs unit tests is identified | ||
|
4. Locate the code for the module |
Source code for the module is located | ||
|
5. Write complete set of unit tests for the module |
Complete set of unit tests is developed for the module | ||
|
6. Post results on the issue tracker |
Results posted to the issue tracker |
Notes for Learning Activities Related to this Pathway
When creating and revising activities:
- Interact with the community to identify likely modules for testing.
- Use an activity that reviews existing unit cases to provide students with an understanding of what they are trying to accomplish.
This category currently contains no pages or media.
