Note: Please note that training delivery does not happen as frequent as it was used to be due to other engagements of the trainer. This applies to both public and corporate training programs. Resumption of training activities to normalcy may not happen very soon. You are kindly requested to seek training from other sources.

Introduction to Test Driven Development with jUnit

When: Tuesday, October 30, 2012 (10.00 AM GMT, 11.00 AM BST)
Find your time: http://www.timeanddate.com/

Enrollment closed for the event on the 30th.   Prefer another time? Let us know.

Description:

Test driven development (TDD) which is also known as test first programming or test infected programming refers to the practice of software developers where they write code test cases before the actual application code is written. This practice enhances the code and design quality of the software, reduces bugs and improves the overall software development efficiency.

JUnit is a Java library that facilitates TDD in Java. It is the de facto standard. It has many extensions and has also been ported to many different programming languages.

Training Objectives:

At the end of the training, participants will be able to

  1. Describe the benefits of test driven development and practice the same.
  2. Design, organize and develop good unit tests with JUnit.
  3. Use JUnit 3 and 4 syntax to code JUnit test cases.

Target Groups:

  1. Java developers

Prerequisites:

  1. You should be familiar with Java programming language. Expert knowledge is not needed.

Communication Language:

English

Duration:

1.5 hours

Facilitator:

Kamal Wickramanayake (Profile)

Training Content:

  1. Introduction to Test Driven Development
    • What is test driven development (or test infected programming)?
    • What is unit testing?
    • Comparing unit testing with debugging
    • Who should write these tests?
    • Qualities expected from a regression testing framework
  2. Introduction to JUnit
    • How to represent a test in JUnit?
    • Test fixture
    • TestCase class and different assertions
    • Running a test
    • Writing JUnit version 3 and 4 test cases
  3. Test Organization
    • Using different source directories for tests and application code
    • Implementing multiple tests within a TestCase
    • Test code skeleton auto generation
    • TestSuites