CS 490M Software Testing
Fall 2006 (Adaptive) Schedule
| Lecture | MWF 9:30am | LWSN B134 |
| Group meetings/Presentations | F 10:30 | LWSN B134 |
| Office Hours: | MW 10:30-11:30am.
Walk-ins welcome, any day/time. |
LWSN 1177 |
| TA | Jorge Ramos.
(Office hours TBA) |
|
SPECIAL TALKS Sudeb Basu, Applied Resources, Inc. Testing the remote-controlled Army drone Friday November 17, 9.30am Craig Abrahamson, Boston Scientific Corporation Testing Cardiac Devices Wednesday August 30, 2006 Peter Shier, Microsoft Frameworks for Testing Windows I/O Drivers Friday, Sptember 1, 2006 |
|||
This page last revised: December 11, 2006
Fridays will be used for team presentations and may require both hours. In lieu of the additional time used on Fridays, the class will not meet during the last week of the semester before the final examination. The second hour on Fridays will be used for team meetings on days when there is no team presentation or exam.
Midterm: October 6, 2006 (9:30am)
Final Exam: Monday Dec 11, 2006 8-10am. LWSN B134
Textbook: Foundations of Software Testing, Draft V3.0, by Aditya Mathur.
| Powerpoint presentations | |||||||||
|
|||||||||
| Week | Date | Topic | Reference | Comments |
| 1 | 8/21 |
Course introduction, Organizational issues, Special lectures and meetings with sponsors. |
Please browse the course web site. | Suggested readings:
An Investigation of the Therac-25 Accidents," IEEE Computer Applications in Power, July 1993, pp. 18-41 |
| 8/23 | Team formation
Project discussion Software testing: Fundamentals-I |
1.1, 1.2, 1.3, 1.4 |
||
| 8/25 | Software testing: Fundamentals-II | 1.5, 1.8., 1.9, 1.10 | ||
| 2 | 8/28 |
Software testing: Fundamentals-III |
1.12, 1.16 | NOT TO BE MISSED! Craig plans to work with the Guidant team to help them understand necessary details of the Test Station. |
| 8/30 |
Special Lecture: Craig Abrahamson, Boston Scientific: Testing Cardiac Devices |
|||
| 9/1 | Special Lecture: Peter Schier, Microsoft: The Windows Driver Model and the Quality Challenge | NOT TO BE MISSED! Peter plans to stay over for the second hour to talk to students working on the Windows driver project. | ||
| 3 | 9/4 |
Labor day. Class does not meet. |
||
| 9/6 |
Test generation from requirements I |
4.1, 4.2 | ||
| 9/8 | Project presentations I | 15 minutes/team: 10 minutes presentattion+5 minutes Q/A. Prepare your slides well. Practice your presentation. At most two members of the team make presentation. | ||
| 4 | 9/11 |
Test generation from requirements II |
4.3 |
Lab 1 assigned (JUnit) |
| 9/13 |
Test generation from requirements III |
4.6 | ||
| 9/15 | Test generation from requirements IV | 4.7 | ||
| 5 | 9/18 |
Test generation from requirements V |
4.7 (continued) | |
| 9/20 | Class does not meet. Instructor away at a conference. | Please use this time to work on the term projects. Thanks. | ||
| 9/22 | Test generation from requirements VI | 4.7 (continued) | Lab 1 due | |
| 6 | 9/25 |
Test generation from requirements VII |
4.7.5 | |
| 9/27 |
Test generation from finite state models I: Strings and FSM basics |
6.1, 6.2 | ||
| 9/29 | Class does not meet, Instructor away at a conference | Please use this time to work on the term projects. Thanks. | ||
| 7 | 10/2 | Test generation from finite state models II: k-equivalence tables | 6.3, 6.4 | |
| 10/4 | Test generation from finite state models III: Constructing the W-set
Midterm review |
6.5 | ||
| 10/6 | Midterm | Readings:
Chapter 1: All sections excluding 1.6, 1.7, 1.11, 1.13, and 1.14. Chapter 4: 4.1, 4.2, 4.3, 4.4, 4.7 (exclude 4.7.6 and BRE adequat etests) Chapter 6: 6.1, 6.2, 6.5 |
||
| 8 | 10/9 | October break. No meeting. | Lab 2 assigned: Bug tracking tool | |
| 10/11 | Midterm solutions summary
Test generation from finite state models IV: FSM Fault model |
6.6 | ||
| 10/13 | Test generation from finite state models IV: W method | |||
| 9 | 10/16 | Test generation from finite state models IV: Applications to OO testing. | Lab 2 due. | |
| 10/18 | Test generation from finite state models IV: Applications to GUI testing. Control theoretic versus automata theoretic, Wp method | |||
| 10/20 | Project Presentation II | 20 minutes/team: 15 minutes presentation+5 minutes Q/A. Prepare your slides well. Practice your presentation. At most two members of the team make presentation. | ||
| 10 | 10/23 |
Test generation: Combinatorial designs I |
12.1, 12.2, 12.3, 12.4 | |
| 10/25 |
Test generation: Combinatorial designs II
|
12.5, 12.6, 12.7 | ||
| 10/27 |
Test generation: Combinatorial designs III
|
12.8, 12.9, 12.11 | ||
| 11 | 10/30 |
Test generation: Combinatorial designs IV |
\ | |
| 11/1 |
|
|||
| 11/3 | Project Review | Lab 3 due. | ||
| 12 | 11/6 | Test adequacy: Control flow based I | 15.1, 15.2 | Lab 4 assigned:
JMeter (performance and load testing) |
| 11/8 | Test adequacy: Control flow based II | 15.2 (continued) | ||
| 11/10 | Test adequacy: Control flow based III | |||
| 13 | 11/13 | Test adequacy: Control flow based IV | Project report outline due.
Lab 4 due. (11/13) |
|
| 11/15 | Test adequacy: Data flow based I | 15.3, 15.4 | ||
| 11/17 | Test adequacy: Data flow based II | 15.4 (continued), 15.7, 15.8 | ||
| 14 | 11/20 | Test adequacy: Data flow based III | 16.1, 16.2, 16.3, 16.4 | Project report draft V1.0 due. |
| 11/22 | Thanksgiving break. No meeting. | |||
| 11/24 | Thanksgiving break. No meeting. | |||
| 15 | 11/27 | Test adequacy: Mutation based | 16.6, 16.7, 16.8 | Lab 5 due (11/29) |
| 11/29 | Applications: OO testing, security testing | 16.10, 16.11, 16.14 | ||
| 12/1 | Course review | Project report draft V2.0 due. | ||
| 16 | 12/4 |
No meeting. (Work on finalizing the project report.) |
Final project report due 12/6
Final Presentations: Presentation: 30 minutes/team plus Q/A. Practice your presentation. At most two members of the team make presentation. Demos (if neeeded) will be a part of this presentation. |
|
| 12/6 |
No meeting |
|||
| 12/8 (Friday) | Final project presentations III:
Video conference in STEW G52 9:30am: Guidant Project 10:30am: Microsoft Project |
|||
| 17 | 12/11 | Final Exam 8-10am LWSN B134 | Final Exam Solution | Comprehensive exam.
Readings: Review all material covered prior to midterm. Plus: Chapter 6: 6.1 through 6.6 Chapter 12: All sections, special emphasis on 12.9, 12.10, 12.11. Chapter 15: All of it, special emphasis on control flow and data flow based adequacy criteria and error detection. Chapter 16: 16.1 through 16.8. Special emphasis on error detection. |