Test-Driven Development in Java - Unit Testing and Refactoring for Agile Software Development
Contact us for Onsite Price
Layout
The training course combines lectures with practical exercises that help the delegates to put what they have learned on the training course into practice. The exercises specifically build on what has been recently taught and are built up as the training course progresses.
Training Course Objectives
- Appreciate the benefits of a continuous and iterative approach to design and delivery
- Recognise the purpose and practice of refactoring in keeping a system supple and adaptable
- Know how to build up a set of unit tests in JUnit
- Understand the consequences of dependency management on testing and code quality
Who it is for
The course is suitable for software developers experienced in Java and familiar with objectoriented principles and practices.
Training Course Prerequisites
- Any previous exposure to JUnit or agile development concepts is beneficial but not essential.
Chapters
Chapter 1 Agile Development Microprocess
- Traditional versus agile development processes
- Iterative and incremental development
- Informal and continuous design
- The role of refactoring
- Refactoring versus other code changes
- Extreme Programming
- Test-Driven Development
Chapter 2 Testing in Principle
- Traditional view and reality of testing
- Driving development through testing
- Testing early, often and automatically
- Testing versus debugging
- White-box versus black-box testing
- Functional versus operational testing
Chapter 3 Basic Unit Testing in Practice
- Test plans versus test code
- Use of Assert
- Testing at the interface
- Testing the simplest things first
- Testing incrementally
- Testing correctness of failure
Chapter 4 Overview of JUnit
- JUnit and the xUnit family
- Test cases, test suites and test runners
- Essential structure of the framework
- Assertion methods
- Testing correctness of exceptions
- Defining common fixture code
- JUnit pattern usage
- Extensions to JUnit
Chapter 5 Test-Writing Techniques
- Red, green, refactor
- None to one to many
- Faking it
- Telling the truth
- Isolated and short tests
- Refactor common fixture code
- Declare, prepare, assert
- Test by method, state or scenario
- Custom assertions
- Compile-time constraints
- Running all tests
Chapter 6 Common Refactorings
- Renaming variables, methods, classes and packages
- Restructuring class hierarchies by extracting interfaces, superclasses and subclasses
- Partitioning classes by extracting classes and methods
- Changing private representation
Chapter 7 Decoupling Techniques
- Unmanaged dependencies
- Test-driven decoupling
- Layering
- Reorganising packages
- Eliminating cyclic dependencies
- Mock objects
- Eliminating Singletons, statics and other globals
- Testing I/O