Software Testing (597), FS 11

Software testing is a major part of software quality assurance. Who is willing to use software that wasn't tested exhaustively? Although most of the developers are aware of the importance of testing, software systems are tested moderately -- often because of time constraints or ignorance.

In this course we present students the fundamentals of effective software testing from the smallest unit to the level of systems. We use well-known open-source tools (such as, JUnit, mockito, Selenium, JMeter, Hudson) for test automation and continuous integration. Presumably the following techniques are presented:

• Test Driven Development
• Unit Testing
• Continuous Integration
• Integration Testing
• System Testing
• Web Testing
• Load and Performance Testing

Students may deepen their software testing knowledge by solving exercises with example applications. We use JUnit in Eclipse to build up test cases and test suites, use mocking frameworks to test in isolation, and use Maven to setup automated Selenium test suites.

The participants know the fundamentals of testing object-oriented software and used them in exercises. Moreover, they are able to test a software system systematically.

The course follows:

• Robert V. Binder. Testing Object-Oriented Systems: Models, Patterns, and Tools. Addison-Wesley, 2000.

Further reading:

• Mauro Pezzè and Michal Young. Software Testing and Analysis: Process, Principles, and Techniques. John Wiley & Sons, Inc., 2008.
• Kent Beck. Test Driven Development: By Example. Addison-Wesley Professional, 2002.

A written exam takes place on Thursday, May 26, 2011 (last course date). In case of a small number of participants, a oral exam takes place instead.

Hinweis: Diese Informationen dienen zur Ergänzung des Vorlesungsverzeichnisses (VVZ). In Zweifelsfällen gelten immer die offiziellen Angaben im VVZ.