Implementing Agile Test Driven Development for Java Developers

Course Details
Code: TT3535-J
Tuition (USD): $1,995.00 • Classroom (3 days)
$1,995.00 • Virtual (3 days)

Implementing Agile Test Driven Development for Java Developers is a three day, in-depth Agile-testing training course that provides experienced Java developers with a solid introduction to Test Driven Development and “test first” design within the context of Agile processes and practices. Test-driven development (TDD) is an evolutionary approach to development where you must first write a test that fails before you write new functional code. This process was developed by Kent Beck and Ward Cunningham. It is primarily an agile approach to software development and is one of the core principles of Extreme Programming.

Skills Gained

Throughout the course, students will be led through a series of progressively advanced topics, where each topic consists of lecture, group discussion, comprehensive lab exercises and review. This is a programming class with many code-based labs that enable students to experience TDD first hand. Working within in a dynamic learning environment attendees will:

  • Be introduced to the concept of development agility and the Agile Manifesto
  • Review each of the major agile development methods underscoring their strengths and weaknesses
  • Understand how to manage an agile environment even within a structured organizational approach
  • Learn how to introduce agility into a development organization
  • Examine what unit testing is and how various xUnit frameworks facilitate unit testing
  • Review and work with the xUnit family of unit testing tools
  • Understand the concepts of and motivations for Test-Driven Development
  • Relate unit testing, test driven development, and test coverage to agile processes
  • Understand the importance of refactoring in supporting agile and test driven processes
  • Work with both refactoring techniques and tools
  • Work with Mock objects to understand what problems they solve and how they accomplish that
  • Understand what Continuous Integration is and what the components of CI are
  • Examine the motivations for CI
  • Review best practices for everything from CI to testing within the context of agile development

Who Can Benefit

This is a intermediary course, designed for software developers. A working knowledge of Java is required. Knowledge of current development processes, such as structured top-down development and the waterfall method is beneficial.

Course Details

Session: Agile Development

Agile Rationale and Concepts

  • Reducing Risk Through Agility
  • The Discipline of Timeboxing
  • Incremental Delivery and Evaluation
  • Agile Method: Scrum
  • Agile Method: XP
  • Pair Programming

The Agile Approach

  • Agile Software Development Manifesto
  • The Agile Principles
  • Identifying Features
  • Managing Features
  • Communication Dynamics

Agile Iterative Development

  • Iterative Approaches
  • Phased Iterative Development
  • Iterating
  • Feasibility & Planning
  • Development
  • Adaptation & Deployment

Prioritizing and Planning

  • Features and Backlogs
  • FDD Process
  • Prioritizing Features
  • Release Planning
  • Assigning Features to Iterations

Building

  • Typical Continuous Integration Process
  • CI Server
  • Automate Source Code Management
  • Automate Build Process
  • Automate Testing
  • Automate Deployment

Session: JUnit

JUnit Overview

  • Purpose of Unit Testing
  • Good Unit Tests
  • Test Stages
  • Unit Testing Vs Integration Testing

Jumpstart: JUnit 4.x

  • JUnit Overview
  • How JUnit Works
  • Launching Tests
  • Test Suites
  • JUnit Test Fixture

@Test Annotation

  • Test Execution Cycle
  • Checking for Exceptions
  • Using Timeouts

Hamcrest

  • About Hamcrest
  • The Hamcrest Matcher Framework
  • Hamcrest Matchers

Parameterized Tests

  • Injecting the Parameters
  • Setting the Parameters
  • Test Execution Cycle
  • Observations

Theories

  • Writing Theory Enabled Tests
  • Defining DataPoints
  • Defining Theories
  • Observations

JUnit Best Practices

  • "Good" Tests
  • Bad Smells
  • White-Box Unit Testing
  • Black-Box Unit Testing
  • Automation and Coverage

Session: Agile Testing Best Practices

Transitioning to Agility

  • Agility: Some Process, Some Mindset
  • Characteristics that Enable Agility
  • Characteristics that Inhibit Agility
  • Risks Associated with Migrating
  • Smoothing the Transition

The Bottom Line

  • Agile Migration Patterns
  • Extending the Migration
  • Coding Practices
  • Source Control
  • Pair Programming and Code Reviews
  • Continuous Integration
  • Legacy Code