View source for DT8021 Ed 2016


==Contact == 

===Lecturer===
[[Mohammad Mousavi]] 

* Office: E 305
* Telephone 035 16 71 22 
* Email: [mailto:m.r.mousavi@hh.se m.r.mousavi@hh.se]

===Schedule===

Lectures: 4 live lectures, 4 recorded lectures

Labs: 3 lab sessions, 1 presentation sessions  

==Objectives==

* Knowledge and understanding
** Explain various classification of test techniques
** Explain behavioral modeling, techniques and model-based testing and test case generation from behavioral models
** Explain the latest research trends in the area of testing and alternatives to testing, particularly, model checking

* Skills and abilities
** Apply the traditional test techniques to realistic examples
** Write abstract behavioral models for embedded systems
** Use the behavioral models in order to perform model-based testing.

* Judgement and approach
** Analyse the suitability of various test techniques given the test assumptions and test goals
** Analyse research results in the field of testing embedded systems


==Assessment==

Assessment is performed in terms of the deliverable of the paper presentation (oral presentation + report), the practical project (software + report) and a written examination.
Each of these will contribute to one-third of the final mark. 


=== [[media:DIT085_assessment_guide_2015.pdf| Assessment Guide 2015]] ===

=== [[media:DIT085_final_examination_march_2015.pdf| Final Examination at Chalmers/GU, March 2015]],   [[media:DIT085_final_examination_march_2015_with_solutions.pdf| Final Examination at Chalmers / GU, March 2015 with Solutions]] ===


=== [[media:DIT085_final_examination_april_2015.pdf| Final Examination at Chalmers/GU, April 2015]],   [[media:DIT085_final_examination_april_2015_with_solutions.pdf| Final Examination at Chalmers / GU, April 2015 with Solutions]] ===


== Slides and Study Material ==

===Slides===

{| class="wikitable"
|-
! Lecture !!  Handouts / Slides !! Other Material 
|-
|  Lecture 1: Terminology and Functional Testing  
April, 2016
||  [[media:DT8021_lecture1_handouts_2016.pdf| Intro: Handouts]]  [[media:DT8021_lecture1_slides_2016.pdf| Intro: Slides]]        

[[media:DT8021_lecture2_handouts_2016.pdf| Functional Test: Handouts]]  [[media:DT8021_lecture2_slides_2016.pdf| Functional Test: Slides]]        

  || 
Chapters 6 and 7 of Jorgensen

Chapters 1 and 4 of Ammann and Offutt

[http://dx.doi.org/10.1002%2Fstvr.4370030203 M. Grochtmann and K. Grimm, Classification trees for partition testing]

|-
|  Lecture 2:  Test Driven Development and Integration Testing 
April 21, 2016
||  

[[media:DT8021_guest_lecture_slides_2016.pdf| TDD and Mocking: Sllides]] 

||   
|-
|  Lecture 3: Coverage Criteria  
Recorded Lecture 
||   
[[media:DT8021_lecture3_handouts_2015.pdf| Handouts]]  [[media:DT8021_lecture3_slides_2015.pdf| Slides]]
 || Chapter 2 Ammann and Offutt
Chapters 9 and 10 of Jorgensen
|-
|  Lecture 4:  Data Flow Testing

Recorded Lecture
||    
[[media:DT8021_lecture5_handouts_2015.pdf| Handouts]]  [[media:DT8021_lecture5_slides_2015.pdf| Slides]]

|| 
|-
|  Practical 1:  Coverage and Data Flow Testing 
April 28, 2016
||  

||   
|-
|  Lecture 5: Model Checking 
Recorded Lecture 
||    
[[media:DT8021_lecture6_handouts_2015.pdf| Handouts]]  [[media:DT8021_lecture6_slides_2015.pdf| Slides]]

|| 
[[media:intro_uppaal_vaandrager.pdf| F. Vaandrager, A First Introduction to Uppaal]] 

[http://www.mbsd.cs.ru.nl/publications/papers/fvaan/handbookuppaal/ Gossip and Jobshop Examples]
|-
|  Practical 2:  Model Checking 
May 4, 2016
||  

||   
|-
|  Guest Lecture: UI Testing    
May 11
||     

|| 

[http://www.cse.chalmers.se/~algeroth/cheatsheet.html VGT Cheat Sheet] (Examples, Exercises)

|-
|  Lecture 6: Slicing and Debugging   
Recorded Lecture 
||    
[[media:DT8021_lecture7_handouts_2015.pdf| Handouts]]  [[media:DT8021_lecture7_slides_2015.pdf| Slides]]
||
Chapters 5, 6, and 13 of Zeller
[http://dl.acm.org/citation.cfm?id=802557 M. Wiser, Program Slicing]
|-
|  Practical 3:  Slicing and Model Examination
May 19, 2016

||  


|-
|}


===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. [http://www.cambridge.org/us/academic/subjects/computer-science/programming-languages-and-applied-logic/reactive-systems-modelling-specification-and-verification Reactive Systems: Modelling, Specification and Verification], Cambridge University Press, 2010.

* A. Zeller. Why Programs Fail? Morgan Kaufmann, 2nd edition, 2009.

* Sujoy Acharya. [http://proxy.lib.chalmers.se/login?url=http://site.ebrary.com/lib/chalmers/Doc?id=10810894 Test-driven development with Mockito]. 

* Marcin Grzejszczak. [http://proxy.lib.chalmers.se/login?url=http://site.ebrary.com/lib/chalmers/Doc?id=10754161 Instant Mockito]. 

* F. Vaandrager, [http://www.mbsd.cs.ru.nl/publications/papers/fvaan/handbookuppaal/  A First Introduction to Uppaal]. In J. Tretmans, editor. Quasimodo Handbook. To appear.

* M. Wiser, Program Slicing, Proc. of ICSE'81, pp.  439-449, ACM, 1981.

== Project Description ==


The practical assignment (called "project" henceforth) is about Test-Driven Development of a communication protocol between two processor boards for  
an autonomous vehicle.
One processor board, henceforth called Arduino, is connected to sensors and periodically sends through a USB channel to the other processor, called  Odroid, 3 values concerning wheel torque, distance measured by the ultrasonic sensor and distance measured by the infrared sensor. 
The other processor is connected to the servo and periodically sends through a USB channel to the first processor speed and steering angle. 

We develop the protocol at the Arduino side as a Java class in a test-driven fashion and integrate it with a mocked  USB channel and Odroid.
Subsequently, we build and test a simple command-line interface that sends and receive messages that makes call to the send interfaces on either sides and 
periodically reads the received values on the other side. 
Finally, we make a model of the protocol and model check its correctness. 


From the testing and verification perspective, the project comprises the application of the following techniques: 

* test-driven development, 
* unit testing using [http://junit.org/ jUnit], 
* gathering coverage metrics using [http://www.eclemma.org/ EclEmma] (or similar tools),  
* integration testing, including developing stubs using [https://code.google.com/p/mockito/ Mockito] (or similar tools), 
* model checking using [http://www.uppaal.org/ Uppaal], and 
* UI testing using the [http://www.sikuli.org/ Sikuli] tool. 

This is a group project that is to be carried out in '''groups of 2'''.  
You need to have formed your groups in GUL and emailed your group structure to the lecturer and both instructors by '''Thursday January 18 at 17:00''';
please put '[DT8021] Group Registration' in the subject line of your email.

The deliverables are to be delivered personally to the lecturer and discussed orally in the presence of all team members.
The deliverables comprise a report and the implementation code: the report should document the major steps in each phase and 
code snippets (few concise examples) of how they are implemented and possibly screen shots of the results. 
Extensive pieces of program code should not be included in the report. 
The most important factors in judging the reports are: their logical structure and sufficiently clear explanation of the steps (all figures and code snippets should be accompanied with clear descriptions).
 
The deadlines are to be respected and each phase is to be sent by an email to the lecturer and discussed with him before the deadline. 

As a general principle, when you find an ambiguity in the requirements, make a reasonable assumption and '''document it clearly''' in your report. 

After you deliver each phase, each and every member of the group should send an email with an estimate of each member's participation in that phase (in percents) and 
the parts of the deliverable each member has contributed to. 


{| class="wikitable"
|-
! Practical !! Deadline !! Notes
|-
|  [[DT8021 Ed 2016 Practical Phase 1|Phase 1: TDD of a Unit]]    ||  April 28, 2016 23:59 || 
|-
|  [[DT8021 Ed 2016 Practical Phase 2|Phase 2: Integration Testing]]    || May 6, 2016 23:59 || 
|-
|  [[DT8021 Ed 2016 Practical Phase 3|Phase 3: UI Testing and Model Checking]]         || May 12, 2016 23:59 || 
|-
|}


==Academic Papers==

Each group is supposed to write a short report on an academic paper and present it in the allocated time-slot. 
The following papers are examples of papers that can be selected for this exercise: 


* [http://dl.acm.org/citation.cfm?id=1806850 Model Checking Lots of Systems: Efficient Verification of Temporal Properties in Software Product Lines]

*  [http://link.springer.com/chapter/10.1007/978-3-319-25945-1_6 Automated Test Design for Boundaries of Product Line Variants]

* [http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1704057 Feature Diagrams: A Survey and a Formal Semantics]

* [http://link.springer.com/chapter/10.1007/11554844_3 Feature Models, Grammars, and Propositional Formulas]

* [http://www.sciencedirect.com/science/article/pii/S2352220816000158 Does this fault lead to failure? Combining refinement and input–output conformance checking in fault-oriented test-case generation]

* [http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=7102600 Perspectives on White-Box Testing: Coverage, Concurrency, and Concolic Execution]

* [http://link.springer.com/chapter/10.1007/978-3-662-49122-5_16 Abstraction-driven Concolic Testing]

The report is to be submitted on May 15; the presentations will be held on May 20. 

==Acknowledgment == 

This course is based on the material produced for several earlier editions given at TU Eindhoven, the Netherlands. 
Part of the material has been produced (or is based on the produced material) by Judi Romijn and Tim Willemse. 
 

=[[Mohammad Mousavi|Back to Home]]=