CS453 Automated Software Testing, Fall 15

Announcement

  • lec23-CREST Examples.pptx
  • Aug 31: The first class starts on Sept 1
  • Sep 22: No class on Sep 29 due to temporarily designated national holiday
  • Sep 24: Linux account will be given to every student to do programming HWs. See Noah BBS for detail.
  • Sep 24: "Overview on testing techniques" on Sep 8 is updated to include the input partitioning technique which is useful for HW#2.
  • Sep 26: Please ask all questions on Noah BBS so that other students can share Q&A and reduce the work of TAs to answer the same questions multiple times.
  • Oct 5: HW#3 is slightly updated to get a regular C file as an input without preprocessing.
  • Oct 12: Q3 and Q4 of HW#3 are slightly updated to receive a preprocessed C file to avoid difficulty of updating macros. See the updated HW#3.
  • Oct 13: No class for Nov 10 and 12 due to Automated Software Engineering (ASE) conference
    • Make-up class: Oct 16 (Fri) 7:00 - 9:30 PM
  • Oct 28: No class for Dec 8 and 10 due to ICSE 2016 Program Board meeting
    • Make-up class: Dec 4 (Fri) 7:00 - 9:30 PM

Administrative Information

  • Instructor: Moonzoo Kim

    Office: 2434 (located at the east wing)
    Phone: 042-350-3543
    E-mail: moonzoo @ c s . k a i s t . a c . k r
    Office hour: Tue/Thur 10:30 AM-12:00
    (reservation e-mail would be preferred)

  • Teaching assistants: Choongwoo Han (cwhan.tunz at gmail.com, x7743), Ji-Hoon Kim (june1116 at kaist.ac.kr, x7747)
  • Lecture hours: Tues & Thurs 9:00 - 10:15 AM
  • Lecture room: 114 (N-1)
  • Prerequisite: experience in C/C++/Java programming and linux/unix command-line utilities.
  • Grading: attendance/class participation/quiz: 20%, HW: 50%, midterm exam: 15%, final exam:15%
    • Late HW will be accepted with 10% penalty of the max score in 1 day, 30% penalty of the max score in 3 days. HW will not be accepted after then.
    • HW should be submitted both in hardcopy and softcopy (through email to TA). 10% penalty of the max score for missing hardcopy or softcopy unless explicitly written in HW.
      • Hint: many questions of exams are from the homework.
    • All programming HWs you submit must be able to replayed by executing a single script file on a TA's verifier account (i.e., submitted HW should not have dependency on your home directory, environment, etc.). Also, the replayed execution must demonstrate the same output to the submitted hardcopy. You will get 10% penalty of the max score otherwise.
      • For your programming HWs, you should not use external libraries which are not available on the verifier machines. If you really need an external library, you have to ask TAs to install it on the verifier machines.
    • More than 7 absences of class will get F grade
      • To start early morning class on time, late attendance shall be considered as 1/3 absence.
      • No excuse for the absence of class except grad students who are occupied by his/her lab activities (e.g., attending conf, etc.) with 1 week prior notice.
  • The official language in the class is English. All students should submit all written documents such as homeworks, project reports, exams, etc. in English; 10% penalty of the max score otherwise.
  • Questions and answers can be done through Noah BBS
  • Excerpts from 강의평가
    • "실질적으로 써먹을 수 있는 내용을 많이 배워서 보람찼습니다"
    • "과제가 많이 어려운것 같았다. 과제에 대한 도움을 수업에서 좀 더 주었으면 좋겠다."

Syllabus

This class covers automated software verification/testing techniques to fight the high complexity of software. The goal of the class is to learn practical applications of advanced verification/testing techniques, not sophisticated theories. These automated techniques can provide high reliability for complex embedded software compared to traditional testing methods in a more productive way. This class guides students to utilize various software verification/testing tools and learn the underlying mechanisms to produce verification results for the target software effectively and efficiently.

Course Material

Course Schedule

Part I: Program coverage criteria and program analysis tools

Part II: Model checking

Part III: Concolic testing (a.k.a., dynamic symbolic execution)

Homework Assignments