Difference between revisions of "DIT085"
From CERES
| Line 17: | Line 17: | ||
Eugene Groshev | Eugene Groshev | ||
| − | * Email: [mailto:groshev@student.chalmers.se] | + | * Email: [mailto:groshev@student.chalmers.se groshev@student.chalmers.se] |
| Line 90: | Line 90: | ||
== Project Description == | == Project Description == | ||
| + | The project is about Test-Driven Development of a [https://www.whatsapp.com/ WhatsApp]-like server- and client-side application. | ||
=[[Mohammad Mousavi|Back to Home]]= | =[[Mohammad Mousavi|Back to Home]]= | ||
Revision as of 05:01, 9 January 2015
Contents
Testing and Verification @ Chalmers / GU - Edition 2015
Contact
Lecturer
- Office: Halmstad University, E 305 (on Fridays at Chalmers: Jupiter, ?)
- Telephone 035 16 71 22 (on Fridays at Chalmers: )
- Email: m.r.mousavi@hh.se
Instructor
Eugene Groshev
- Email: groshev@student.chalmers.se
Objectives
- Knowledge and understanding:
- describe the distinction between software verification and software validation;
- name and describe basic concepts on testing, as well as different testing techniques and approaches
- describe the connection between software development phases and kinds of testing;
- exemplify and describe a number of different test methods, and be able to use them in practical situations.
- Skills and abilities:
- write models in at least one formal specification language;
- construct appropriate and meaningful test cases, and interpret and explain (to stakeholders) the results of the application of such test cases ( using appropriate tools) to practical examples
- plan and produce appropriate documentation for testing
- apply different testing techniques on realistic examples.
- Judgement and approach:
- exemplify and describe tools used for testing software, and be able to use them and interpret their output
- exemplify and describe the area of formal verification in general, including model checking and runtime
- verification, and its relationship to software quality.
- identify and hypothesize about sources of program failures, and reflect on how to better verify the correctness of such programs.
Assessment
Assessment is performed in terms of the deliverable of the practical project (software + report) and a written examination.
- To obtain a Pass (Godkänd: G) mark for the course, the student must obtain a Pass mark for both the project report and the written examination.
- To obtain a Pass with Distinction (Väl godkänd : VG) mark for the course, the student must obtain a Pass with Distinction mark for both the project report and the written examination.
- Otherwise, the student will fail the course and obtain a Fail mark (Underkänd: U).
Slides and Study Material
| Lecture | Handouts / Slides | Other Material |
|---|---|---|
| Lecture 1: Terminology and Functional Testing | Chapter 4 | |
| Lecture 2: Test-Driven Development and jUnit | ||
| Lecture 3: Coverage Criteria | Chapter 2 and 3 | |
| Lecture 4: Slicing and Debugging |
Main Textbook
P. Ammann and J. Offutt. Introduction to Software Testing. Cambridge, 2008.
Recommended Reading Material
- P.C. Jorgensen. Software Testing: A Craftsman’s Approach. Auerbach Publications, 3rd edition, 2008.
- L. Aceto, A. Ingolfsdottir, K.G. Larsen, and J. Srba. Reactive Systems: Modelling, Specification and Verification, Cambridge University Press, 2010.
Project Description
The project is about Test-Driven Development of a WhatsApp-like server- and client-side application.
