1. Schedule Tuesday April 17: First public code checkin – Initial dominion implementation; MUST define all functions, have a “working” (not bug free!) dominion – Place in PROJECT/dominion-code/ Tuesday April 24: First test report due – Report goes in PROJECT/report1/ – Tester code goes in PROJECT/tester-code/ Tuesday May 15: Second test report due – You can guess where report goes. Update tester-code. Tuesday June 5th: “Late Midterm” in class June 11: FINAL TEST REPORT DUE, PROJECT MUST BE COMPLETED

2. Grading & Other Admin Stuff Project: 75% Late “midterm”: 15% (Possibly-in-class) quizzes/exercises/homework: 10% My office hours: Wed, 11-12:30 or by appointment! Or just email me (fastest turnaround for simple things) KEC 3067

3. Testing Project Start with: interface and a chunk of (buggy) code – Implement one function – Start writing tests! Have a “clean” suite that will run for your/others’ code Apply tests to other students’ code and submit bug reports in the repository – Write periodic test reports informing “management” what you’ve done – More info in project-info slides

4. Testing Project Grading criteria – Effectiveness of your testing approach: coverage, bugs found, depth/interest, originality of ideas! – Quality of test/bug reports Can I figure out how you tested the system? Can I figure out what wasn’t tested? Can I figure out how reliable you think the code is?