Background for the header
To the home page of the University of Antwerp

 

 

Time Schedule | Industrial Guest Speakers | CourseMaterial | Exam

LORE / Teaching / Software Testing

The exam is scheduled for Tuesday, june 14th in Prof. Demeyer's office (Room CMI.G.106b). We will discuss for approximately 1/2 and hour about (a) a randomly selected chapter of the software testing book (not one you presented yourself); (b) a randomly selected invited lecture; (c) the test techniques and strategies applied during the lab session.

You can bring annotated copies of all material used during the lectures.

The fine-grained schedule for the project defenses (30 minutes per student).

9:30 - AKOS Nagy
10:00 - BAETENS Nick
10:30 - BUYL Kevin
11:00 - DE COCK	Matthias
11:30 - DE HEN Dieter

-- lunch break
        
13:00 - DE SMEDT Philip
13:30 - DE VYLDER Thomas
14:00 - LOOTS Gertjan
14:30 - RIEGELHAUPT Daniel
15:00 - SAQUET Tim

-- short break

15:45 - SLOWACK Jelle
16:15 - SMETS Bart
16:45 - VAN LOON Glenn
17:15 - VERHEYEN Tom

If names are missing from the above list, or if you spot any other mistakes, please contact prof. Serge Demeyer immediately.

Students: Master Computer Science
Period: 2nd semester 2010-2011

From the academic year 2009-2012 onward, this course will be offered every 2 years. It will not be offered in 2009-2010; 2011-2012; ... but will be offered in 2010-2011; 2012-2013; .... The motivation for this organisation is the fact that this course explicitly invites industrial guest speakers; a feature well-appreciated by the fellow students. Offering the course every two years must guarantee that these industrial lectures attract sufficient participants.

Professor: Prof. S. Demeyer

Assistants: Ahmed Lamkanfi, Jan Vlegels.

Theory
Time: Tue 08:30 - 10:30
Location: CMI.G.005 (Campus Middelheim)
Exercises
Time: Wed 08:30 - 10:30
Location: CMI.G.027 (Campus Middelheim)

Prerequisites

Before starting this course a student should have:

  • Practical programming experience with an object-oriented programming language(e.g., Java, C++), preferably in a team context.
  • Basic awareness about the testing of software (unit tests, regression tests).
  • Knowledge about the various techniques used in the different phases a software project (requirements, analysis, design, implementation, testing, maintenance).
  • Knowledge about techniques for managing quality during a project (cost estimation, code reviews, metrics).

The easiest way to satisfy these prerequisites is to have a passing grade for the course Software Engineering (BA 3 Computer Science).

Course content

De student will acquire experience with thorough testing and verification of a software system, to guarantee with a certain degree of confidence that a given software system meets its specification.

The course has a practical ring to it with a minimal theoretical content (taught as testing patterns; students have to deliver some of the lectures themselves), several lab-sessions (trying out several test techniques and strategies on an existing software system) and industrial guest speakers illustrating how testing is done in real projects.

From the academic year 2009-2012 onward, this course will be offered every 2 years. It will not be offered in 2009-2010; 2011-2012; ... but will be offered in 2010-2011; 2012-2013; .... The motivation for this organisation is the fact that this course explicitly invites industrial guest speakers; a feature well-appreciated by the fellow students. Offering the course every two years must guarantee that these industrial lectures attract sufficient participants.

Objectives (expected learning outcomes)

After this course, a student will be able to

  1. apply white-box and black-box testing techniques to set-up a test-suite;
  2. assess and improve the coverage of a test suite;
  3. select the most appropriate test strategy;
  4. conduct review sessions to verify a specification for a software system.

Practical Organisation (incl. Time Schedule)

Theory
The course starts with a few introductory lectures by prof. Demeyer. Afterwards each student will prepare part of a lecture based on a chapter in the book Testing Object-Oriented Systems. (Robert V. Binder); Addison-Wesley, 2000. We will use peer review to rate the quality of the lectures using the following criteria [CriteriaSwTestingMAS.doc].
At the end of the semester the course features a few invited speakers from a testing department / QA department in the software industry; they will share their experiences on testing practices in an industrial context.
Exercises
During the exercise session you will experiment with numerous test techniques and strategies on a small yet representative system, namely a simplified version of the famous pac-man game.

Below is the detailed time-schedule, which is subject to change. Changes will be notified over e-mail. [Last modified on: Monday, February, 14th 2011.]

Theory

		Tuesday 8:30-10:30 - G.005
1	15-Feb	[T] Introduction (Ch. 3 en 4)
2	22-Feb	[T] Test Models (Ch. 5 - 7)
3	01-Mar	[T] Ch.9 (Results) + Ch.10 (Classes)
4	08-Mar	 -- no lecture
5	15-Mar	[S] Ch.11 (Components) + Ch.12 (Subsystems)
6	22-Mar	[S] Ch.13 (Integration) + Ch.14 (Application)
7	29-Mar	[S] Ch.15 (Regression) + Ch. 17 (Assertions)
8	05-Apr	[S] -- spare slot
	12-Apr	 -- easter holiday
	19-Apr	 -- easter holiday

Industrial Guest Speakers

9	tue 26-Apr 9:00 - 10:30    Steven Mertens (the test leaders) [Test consultants]
 	wed 27-Apr 9:00 - 10:30    Patrice Willemot and Petra Haldermans(ctg) [Test consultants]
10	03-May	  9:00 - 10:30 Olivier De Lissnyder (AXA)  [Banking]
11	10-May	  9:00 - 10:30 Ivo Neyens (Alcatel-Lucent) [Telecommunication]
12	17-May	  9:00 - 10:30 Luc Hermans (LMLS International) [Automotive Simulation]

Student lectures

5	15-Mar	[S] Ch.11 (Components) + Ch.12 (Subsystems)
	AKOS Nagy
	BAETENS	Nick
	BUYL	Kevin
	DE COCK	Matthias
	DE HEN	Dieter
        
        >> Opponents: group of week 7

6	22-Mar	[S] Ch.13 (Integration) + Ch.14 (Application)
	DE SMEDT	Philip
	DE VYLDER	Thomas
	LOOTS	Gertjan
	RIEGELHAUPT	Daniel
	SAQUET	Tim

        >> Opponents: group of week 5

7	29-Mar	[S] Ch.15 (Regression) + Ch. 17 (Assertions)
	SLOWACK	Jelle
	SMETS	Bart
	VAN LOON	Glenn
	VERHEYEN	Tom

        >> Opponents: group of week 6

Probably not participating anymore
	CASTELL EGEA	Isidoro
	ORSZAGH	Sandor
	PAUWAERT	Tom
	ROBERTO	Francisco Javier

Exercises

		Wednesday 8:30 - 10:30 - G.027
1	16-Feb	 -- no lecture
2	23-Feb	[P] Java testing tools
3	02-Mar	[P] Category Partitioning and Boundary Values
4	09-Mar	[P] Enforcing proper associations with asserts
5	16-Mar	 -- no lecture
6	23-Mar	[P] Decision Structures
7	30-Mar	[P] State Machines
8	06-Apr	[P] Wrap up
9	13-Apr	 -- easter holiday
10	20-Apr	 -- easter holiday
	27-Apr	[P] -- spare slot
	04-May	 -- no lecture
11	11-May	[P] -- spare slot
12	18-May	[P] -- spare slot
13	25-May	[P] -- spare slot

Course Material

The book Testing Object-Oriented Systems. will be used heavily during the sessions. Several copies are available in the library (see http://anet.ua.ac.be/record/opacua/c:lvd:3072797). Buying the book for the course is not necessary.

 book cover

Besides the book, there are the copies of the slides used during the lectures (of which the originals are available in keynote):

The presentation material from the industrial guest speakers

For the exercise session in the computer lab here is the course material:

Exam

The exam is organised as an oral round where you will be questioned for approximately 1/2 and hour on (a) the application of white-box and black-box test techniques to set-up a test suite; (b) the calculation of the coverage of a given test suite; (c) choosing the most appropriate test strategy; (c) verifying a given test-model of a system.

The final grade will be based on four components:

(a) Student lecture:
Each student will teach one part of a lecture, and your colleagues will peer review your contribution based on a given criteria check-list.
The criteria check list can be found at [CriteriaSwTestingMAS.doc]
(b) Guest lecture:
You will be questioned on one of invited guest lectures (random selection).
(c) Lab-sessions:
You must argue which of the applied test techniques and test strategies are most useful ? which could be improved ? why ?
(d) Testing patterns:
You will be questioned on one of the chapters in the book (randomly selected, but not one which you taught yourself). During this questioning you may consult the book (a copy will be present during the exam), and your own notes (which you should bring yourself).

 
Valid HTML 4.01! Valid CSS!

 Lab On REengineering - Antwerpen, last modified 11:17:12 07 June 2011