In4matx 115: Software Testing, Analysis, and Quality Assurance

Overview

Software testing is more than just error detection.It plays an important role in Software development lifecycle by improving the quality, reliability & performance of the system by checking what the software is supposed to do and also checking that the Software is not doing what its not supposed to do. After the completion of the course, students will be able to

• Describe the cost-benefit trade-offs inherent in the use of automated tools for building software and configuration management
• Describe several techniques for validating and measuring the quality of software
• Apply testing techniques, including black-box and white-box techniques, automatic testing activities, and regression testing
• Use appropriate techniques and tools, including a debugger, to locate program faults
• Describe several types of maintenance processes associated with correcting and enhancing software systems
• Participate effectively in a software inspection

General Information

• Instructor: Professor Iftekhar Ahmed, iftekha@uci.edu
• Lectures: Tu,Th 06:30-07:50
• Class Location: Humanities Instructional Building HIB 100
• Instructor Office Hours: After class and by appointment
• Course TAs:
• Nishitha Shankar Suvarna nssuvarn@uci.edu
• Pritha Dawn pdawn@uci.edu
• Aishwariya Rao Nagar arnagar@uci.edu
• TA Office Hours: TBA
• Course Materials: Canvas
• Web Forum to ask questions and discussion:Piazza

Description

• Course Prerequisites: I&C SCI 45J or I&C SCI 45C or I&C SCI 46 or CSE 46 and IN4MATX 43 with a grade of C or better.
• Requirements and Expectations of Students: This course requires a strong programming background and a good understanding of complex programs. There will be homeworks and projects that require programming. As such, I expect students to be familiar and comfortable with programming. We will mostly focus on Java, but may include other languages - so a comfortability and eagerness to learn new programming languages is important. The assignments/projects will have high level descriptions, intentionally vague in some cases, to mimic real world experience.

Topics

• Testing Fundamentals
• Specifications
• Combinatorial Testing
• Structural Testing
• Fault-based Testing
• Regression Testing
• Testing Object-Oriented Programs
• Testing Process
• Debugging

Tentative Schedule

This schedule is subject to change

Policies

Grading

Grading weights: 10% for each of the 4 assignments (Total 40%),20% Midterm exam, 20% Final exam,15% Final Project, 5% Quiz

Assignments - 40%
* There are 4 total assignments to be completed over the course of this class.
* Assignments include a mixture of written documents and code submissions.
* Assignments are all submitted via checking in to the git repository for the class!
* If you have a problem with an assignment grade, you must contact the instructor through EMAIL within ONE WEEK of receiving your grade.
* Be forewarned that every single assignment will require a lot of work. Do not wait until the night before to start the homework; you will be dismayed. Start on each homework the week before it is due, and spread the work throughout the week.

Midterm Exam - 20%
* These tests are designed to take 60-90 minutes each.
* If you have a problem with the grade, you must contact the instructor through EMAIL within ONE WEEK of receiving your grade.

Final Exam - 20%
* These tests are designed to take 60-90 minutes each.
* If you have a problem with the grade, you must contact the instructor through EMAIL within ONE WEEK of receiving your grade.

Final Project - 15%
* There is a final project designed to check for a cumulative understanding, which includes some of the work for assignments.
* Final project include a mixture of written report and code submission.
* For this project, you will work alone.
* Like assignments, all submission is via CANVAS.
* Like assignments be forewarned that the project will require a lot of work. Do not wait until the last moment to start; you will be dismayed. Start as early as possible.
* If you have a problem with the grade, you must contact the TA through EMAIL within ONE WEEK of receiving your grade.

Cheating

The UCI academic honesty policy applies. Consequences of cheating in this class: a letter in your UCI file, and the course grade is lowered, most likely to F. Material that is copied from any source needs to be quoted and the source must be cited. If you plagiarize, you run the severe risk of failing the class, in a most disgraceful manner. All work should be assumed to be individual work (not group work) unless stated otherwise on the assignment.

Students with Disabilities

If you need an accommodation because of a disability, please contact the instructor and the Disability Services Center as soon as possible.

Additional Resources

Most of this course was adapted from teaching material designed by Dr. James A. Jones.

Last Updated: November 3, 2019