Category:Create Unit Tests (Pathway)
(Difference between revisions)
| Line 50: | Line 50: | ||
|- | |- | ||
| | | | ||
| − | 3. | + | 3. Identify module(s) that lack tests, need improved and/or additional unit tests |
| + | *Examine test plan/documentation, if it exists | ||
| + | *Seek advice of community members for necessary testing | ||
| + | *Identify test framework and run test coverage tools | ||
| Module that needs unit tests is identified | | Module that needs unit tests is identified | ||
| | | | ||
Revision as of 00:17, 9 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. Build and run the project |
Project is built and executed | ||
|
3. Identify module(s) that lack tests, need improved and/or additional 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.
