Description

Instructor:
Sudipto Ghosh
Office: 468 CS Building
Office Hours: Wed 9-10, Thurs 9-10
Email: ghosh@colostate.edu
GTA:
Phillipa Bennett
Office: CSB 120 lab
Office Hours: Thu 11-1
Email: plarreeb@colostate.edu
Lecture Time and Place:
10:00-10:50 AM, MWF, COMSC 325

Students will learn and apply state-of-the-art techniques for analyzing and testing programs. Students will be able to automatically (1) generate test inputs for testing programs, (2) measure coverage during test execution, (3) localize faults in a program, (4) explore program repair techniques. This course prepares students for practical work in the software industry by exposing them to the latest approaches and tools. This course also prepares students who are interested in cutting-edge research in software testing and analysis.

The topics covered in this course are listed below:

  • Overview of software testing and preliminaries
  • Black-box testing
  • White-box testing
  • Syntax-based testing (includes mutation testing)
  • Higher order mutation
  • Test input generation (random, guided random, model-based, symbolic, concolic, SMT solvers)
  • Fault localization techniques (spectrum-based, delta-debugging, other types)
  • Program repair
  • Regression test selection
  • Test case prioritization

Students will be exposed to software tools that implement various testing approaches.

Prerequisites

CS414 (Object-Oriented Design) or permission of instructor.

Communication with instructor and GTA

You must have a Colorado State University eIdentity (eID), before you can be installed into the CS580A5 Canvas system. The CS580A5 Canvas page will have all of the course notes, assignments, discussions, and exams, so it is very important for you to be installed on this system. Visit the eIdentity and eServices web page to get your eID. You will not be able to take part in the course until you have an eID.

All queries to the instructors should be sent by email to ghosh@cs.colostate.edu or posted only on the Main discussion group. Queries posted on any other discussion group will not be monitored.

The first day of class is Wednesday, January 20, 2016. Be ready to start then. Go to the Progress page to view the weekly schedule. The on-campus class meets on Mondays, Wednesdays, and Fridays.

Materials

  • Required Texts:

    1. Paul Ammann and Jeff Offutt, Introduction to Software Testing, Cambridge University Press, Cambridge, UK, ISBN 0-52188-038-6, 2008

  • Other material:

    • Video recordings of lectures will be available via Canvas.
    • Powerpoint slides will be available on Canvas under Modules->Slides.
    • Papers from journals and conference proceedings

Grading

Here are the formally graded elements of the course and associated weighting:

Activity Weight
Assignments 40 %
Discussion assignments on Canvas 10 %
Midterm 15 %
Final exam 15 %
Term project 20 %

Final letter grades will be based on the relative distribution of total scores and not on any preset numerical grade.

Assignments need to be turned in electronically via Canvas by 11:59 pm on the due date.

There will be a term project that involves writing a term paper. Students should identify topics by Spring Break.

Students must actively participate in the discussion forums on Canvas to get a grade in discussion assignments. Each discussion group will have about 4-5 members. While specific instructions will be given for each discussion assignment, in general, we expect each student to make an initial posting for each assignment, followed by responses to other students' postings. Merely having one sentence that says, for example, "I agree with everyone", is not enough to get a grade.

There are two exams (midterm and final). Exact dates will be announced later.

We will be glad to re-grade the same submission if you feel that there was a mistake in grading. Contact us within 4 calendar days for a re-grade. Work will be re-graded in its entirety, and may result in an increase, decrease, or no change in the grade. Note that, once we have graded an assignment, we will not allow you to re-do and re-submit it for grading.

Late and Makeup Policy

  • Late work will not be accepted without prior permission. If you cannot finish the work by the deadline, contact the instructor as soon as possible. Extensions will be granted on a case-by-case basis and are more likely when permission is sought in advance, for reasons which are unexpected and beyond your control, and which involve only a short extension. The instructors reserve the right to assign a score penalty to the late work, depending on the circumstances and degree of lateness.

  • Late penalties for design and discussion assignments are as follows:
    • Up to 12 hours late: 10% penalty
    • 12 to 24 hours late: 25% penalty
    • 24 to 48 hours late: 50% penalty
    • More than 48 hours late: No credit

    Note that the percentages refer to the total points available for the deliverable, not the points that you have received. That is, if an assignment is worth 100 points, and you get 76 and are 7 hours late, you will receive 66 points.

  • Exams may not be taken or submitted after the due date.

  • If you miss an exam, you receive a score of zero.

Professional Conduct

All students are expected to conduct themselves professionally. We (the instructors and GTAs) assume you are familiar with the policies in the student information sheet for the department and the department conduct code. Additionally, you are computing professionals, albeit perhaps just starting. You should be familiar with the code of conduct for the primary professional society, ACM. You can read the ACM Code of Conduct HERE.

This course will adhere to the CSU Academic Integrity Policy as found in the Student Conduct Code. At a minimum, violations will result in a grading penalty in this course and a report to the Office of Conflict Resolution and Student Conduct Services.

Students not already familiar with the CSU Honor Pledge should review this clear and simple pledge and always adhere to it. Academic dishonesty will be dealt with severely. The first instance of cheating will result in negative credit. The second instance will result in a failing grade and other penalties dictated by departmental and university policies.

We work to maintain an environment supportive of learning in the classroom and laboratory. Towards that end, we require that you be courteous to and respectful of your fellow participants (i.e., classmates, instructors, GTAs and any tutors). In particular:

  • Please turn off the ring on your cell phone. If you are expecting an emergency call, sit near the door and slide out discretely to take it.
  • In class use of electronic devices in general, and laptops specifically, is permitted as a courtesy so that you may better participate and learn. If at any time the instructor judges that an electronic device is becoming a distraction the student may be asked to to turn it off and put it away.

We require you to follow the guidelines listed below for postings on Canvas:

  • Be professional.
  • Be courteous.
  • Do not post any questions about your grade or any grading issues. Such questions are private communication and must be emailed.
  • Do not post any opinions regarding your graded assignment, or any aspect of the course. You will have a chance to submit anonymous reviews at the end of the semester. Email feedback to the instructor regarding the course is acceptable and welcome.
  • The instructor reserves the right to delete postings that do not promote a conducive learning experience for students in the class.