Happy testing :-)

Happy testing :-)

Some follow up information from the week 3 lecture.

A2.2 answers are available in CS3215 Supplementary notes . This should help to double check your understanding of the spec, which is vital to system testing.

IVLE forum is locked (you can still see the old posts though). Please use the Google group for class discussions.

Consultations during next week (Feb 2-6) are to be done in a project meeting fashion. Important things: there should be an agenda, there should be some one (meeting chair) to guide the meeting, and important decisions should be recorded (by scribe) and later circulated. We'll be there in an observer capacity.

Reading list for this week has been updated with the below.

Required:

• Tips for planning and tracking the project (googledoc)
• Tips for running a project meeting (googledoc)
• Tips for using tools (googledoc)
• Tips for tackling project risks (googledoc)
• Section "Guidelines for tracking individual contribution" from CS3215 Supplementary notes (googledoc)

Optional:

• This page (external link, read at your own risk :-) contains some jokes about software testing
• 20 Famous Software Disasters - think about these when you take a shortcut in a project task. Do you want to be the one who caused one of these? :-)

There are some justifiable requests to keep the schedule in Google calendar format as well. Please give us some more time to come up with a solution acceptable to all.

Happy testing!