Difference between revisions of "FND-CSC-Test driven development"
m |
m |
||
| Line 27: | Line 27: | ||
<div id="ABC-unit-framework"> | <div id="ABC-unit-framework"> | ||
== Abstract == | == Abstract == | ||
| + | <section begin=abstract /> | ||
<!-- included from "../components/FND-CSC-Unit_testing.components.wtxt", section: "abstract" --> | <!-- included from "../components/FND-CSC-Unit_testing.components.wtxt", section: "abstract" --> | ||
... | ... | ||
| + | <section end=abstract /> | ||
{{Vspace}} | {{Vspace}} | ||
| Line 62: | Line 64: | ||
*<b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit. | *<b>Time management</b>: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit. | ||
<!-- included from "ABC-unit_components.wtxt", section: "deliverables-journal" --> | <!-- included from "ABC-unit_components.wtxt", section: "deliverables-journal" --> | ||
| − | *<b>Journal</b>: Document your progress in your [[FND-Journal| | + | *<b>Journal</b>: Document your progress in your [[FND-Journal|Course Journal]]. Some tasks may ask you to include specific items in your journal. Don't overlook these. |
<!-- included from "ABC-unit_components.wtxt", section: "deliverables-insights" --> | <!-- included from "ABC-unit_components.wtxt", section: "deliverables-insights" --> | ||
| − | *<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|insights! page]]. | + | *<b>Insights</b>: If you find something particularly noteworthy about this unit, make a note in your [[ABC-Insights|'''insights!''' page]]. |
{{Vspace}} | {{Vspace}} | ||
Revision as of 17:32, 7 September 2017
Unit Testing Best Practice
Keywords: Unit testing and Test Driven Development
Contents
This page is only a stub; it is here as a placeholder to establish the logical framework of the site but there is no significant content as yet. Do not work with this material until it is updated to "live" status.
Abstract
...
This unit ...
Prerequisites
You need to complete the following units before beginning this one:
Objectives
...
Outcomes
...
Deliverables
- Time management: Before you begin, estimate how long it will take you to complete this unit. Then, record in your course journal: the number of hours you estimated, the number of hours you worked on the unit, and the amount of time that passed between start and completion of this unit.
- Journal: Document your progress in your Course Journal. Some tasks may ask you to include specific items in your journal. Don't overlook these.
- Insights: If you find something particularly noteworthy about this unit, make a note in your insights! page.
Evaluation
Evaluation: NA
- This unit is not evaluated for course marks.
Contents
...
Further reading, links and resources
Notes
Self-evaluation
If in doubt, ask! If anything about this learning unit is not clear to you, do not proceed blindly but ask for clarification. Post your question on the course mailing list: others are likely to have similar problems. Or send an email to your instructor.
About ...
Author:
- Boris Steipe <boris.steipe@utoronto.ca>
Created:
- 2017-08-05
Modified:
- 2017-08-05
Version:
- 0.1
Version history:
- 0.1 First stub
This copyrighted material is licensed under a Creative Commons Attribution 4.0 International License. Follow the link to learn more.
