1. cs498dm Software Testing Darko Marinov January 24, 2008

2. Administrative Info FAQ: Structure of problem sets? (5*15%) –Mix (roughly 50:50) of MP (Java) and non-MP –You can take a look at previous examples http://www.cs.uiuc.edu/class/sp06/cs498dm/pset4.pdf http://www.cs.uiuc.edu/class/sp06/cs498dm/pset3.pdf http://www.cs.uiuc.edu/class/sp06/cs498dm/pset2.pdf http://www.cs.uiuc.edu/class/sp06/cs498dm/pset1.pdf How will project look like? (25%) –Describe your testing of a refactoring engine –Mostly manual, some automated

3. Textbook “Introduction to Software Testing” by Paul Ammann and Jeff Offutt Arrived in the authors’ bookstore Should be here soon –I called the bookstore, and it’s not here yet –“Bug” in Google: search for “u of i bookstore”

4. Previous Lectures Introduction on “Bugs” –Why look for bugs? –What are bugs? –Where they come from? –How to detect them? Refactoring –What it is? –Why you need it? –How to perform it?

5. Today’s Lecture: Example Interactive Testing Session Test some small program or a refactoring –EncapsulateField: Replace field accesses with setters and getters –TriTyp: Given three integers for the lengths of the sides of a triangle, find the type of triangle Several reasons to do this together –We will learn some testing terminology –It should be fun to look for some bugs –We can learn from mistakes as we go

6. Testing Levels Based on Software Activity Unit testing (Module testing) Integration testing System testing (Acceptance testing) Regression testing Names are not standardized –I don’t insist on names; we will follow the book

7. Test Cases Test case values (inputs) Expected results (if known) Prefix values Postfix values –Verification values –Exit commands Test set/suite: a set of test cases

8. Some Other Terminology Black-box testing White-box testing (or glass-box, clear-box) Top-down testing Bottom-up testing Static testing Dynamic testing

9. Coverage Criteria Did we have any test plan or purpose? Did we specify any test requirements? How good are our tests? Did we generate enough tests? Criterion: rule that imposes test requirements Coverage: satisfaction of test requirements

10. Next Lecture Tuesday, January 29 We will look deeper into coverage criteria If you don’t know JUnit, read about it –http://junit.sourceforge.net/ –See “JUnit Cookbook” or “Test Infected - Programmers Love Writing Tests” Assignment: try some refactorings –Think which you’d like to test –Discuss ideas with me