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

• Reading: Testing Your Procedures
• Lab: Unit Testing with RackUnit
• EBoard (Source) (HTML)

Overview

• Why test?
• Strategies for testing.
• The primary testing operations.

Administrivia

• Maintain lab partners from Friday.
• No lecture after preliminaries today.
• Quick observations from prologues.
  • Folks are worried about how to do the checkerboard concisely. (I hope that you're not worried about how to do the checkerboard.)
  • Many problems are, indeed, relatively close to the problems on the procedures lab. Getting the details right (and making sure that you have the details right) will be a bit hard.
• I'm glad to see that many of you used the Sunday afternoon tutor session. Thanks Alex!
• Quiz 2 returned.
  • Because of difficulties on the quiz, I'm playing with the schedule a bit.
  • I'll probably use the first half of Tuesday's class to talk about issues from the quiz. (I sent you notes yesterday afternoon.)
• Notes on HW 2 distributed.
  • Let me know if you have questions.
• There's a request that I keep things in the top 2/3 of the screen. I'll do my best to do so. If I fail, please let me know.

Upcoming Work

• Lab writeup (due Wednesday): (No Writeup)
• HW 3 due Tuesday night.
• Reading for Tuesday:
  • Design and Color

Campus Events of Interest

• Rosenfield seminar on Scotland, Tuesday noon and Thursday afternoon.
• Rebecca Hamlin book talk Wednesday at 4:15 pm.
• Internship talks Wednesday and Thursday afternoons.

Extra Credit Opportunities

Academic

• Convocation Wednesday: President Kington
• CS Table Friday: Browser Tracking

Peer Support

• Football Games (???)
• Women's Volleyball (???)
  • Congrats on three victories this weekend!
• Men's Tennis (???)
• Women's Tennis (???)
• Anna Christie, Oct. 9-12 (SB plays Marthy)

Most of my thoughts on testing have ended up in the reading.

Basic Idea

• We verify the correctness of procedures by running tests that compare predicated values to actual values.

Model

• We do a single comparison with check-equal? (or some variants).
• We group one or more comparisons into a test case with test-case. That lets us add a description to the checks.
• We group one or more tests or comparisons into a test suite with test-suite. Unlike test-case, which runs the test,, test-suite builds a value that you run later.