Functional Problem Solving (CSC 151 2014F) : Outlines
Primary: [Front Door] [Schedule] - [Academic Honesty] [Disabilities] [Email] - [FAQ] [Teaching & Learning] [Grading] [Rubric] - [Calendar]
Current: [Assignment] [EBoard] [Lab] [Outline] [Reading]
Sections: [Assignments] [EBoards] [Examples] [Handouts] [Labs] [Outlines] [Readings]
Reference: [Setup] [VM] [Errors] - [Functions A-Z] [Functions By Topic] - [Racket] [Scheme Report (R5RS)] [R6RS] [TSPL4]
Related Courses: [Davis (2013F)] [Rebelsky (2014S)] [Weinman (2014F)]
Misc: [Submit Questions] - [SamR] [Glimmer Labs] [CS@Grinnell] [Grinnell] - [Issue Tracker (Course)]
Held: Monday, 15 September 2014
Back to Outline 09 - Side Effects: Images, Output, and More. On to Outline 11 - A Design Perspective.
Summary
We consider testing: When, why, and how you might test the procedures and the programs you write.
Related Pages
Overview
Administrivia
Most of my thoughts on testing have ended up in the reading.
check-equal?
(or some variants).test casewith
test-case
. That lets us add a description to the checks.test suitewith
test-suite
. Unlike test-case
, which runs the test,, test-suite
builds a value that you run later.