Test-Driven development in C# and Java

Fakta
Hvor
København
Hvornår
22. - 23. sep 2016
Tidspunkt
09:00 - 17:00
Underviser
Kevlin Henney
Sprog
Engelsk
Pris
kr. 12.500 ex. moms

This two day Test-Driven Development in C# & Java course presents a number of modern practices for developing code based on an adaptive development lifecycle.

Agility and predictability are two qualities often missing from software development. A test-driven approach, in which design is grown and code delivered incrementally according to functionality or risk, forms the basis of the construction phase of an iterative and incremental development. The use of unit testing provides confidence in existing code and supports the ability to refactor code as development unfolds.

The course is intended as a practical course: the best way to appreciate how test-driven development works and what it feels like is to do it in practice, making sense of the principles it embodies. In this form the course is based on lecture material, demonstration, discussion, exercises and hands-on labs.

Learning Objectives

  • Appreciate the benefits of testing as a design tool and not just a defect reduction technique
  • 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 NUnit/JUnit
  • Understand the consequences of dependency management on testing and code quality.

Audience

The course is suitable for software developers experienced in C# or Java and are familiar with object-oriented principles and practices. Any previous exposure to NUnit/JUnit or Agile development concepts is beneficial but not essential.

Agenda

Programmer Testing
Evidence of care
Testing viewpoint
Pragmatic testing
Automation Bug pathology
Qualitative and constructive

Good Unit Tests
Test quality
Good unit tests (GUTs)
Not-so-good unit tests
Fine-grained tests
Behavioural tests
Functional versus operational testing
Black-box tests

Overview of JUnit and NUnit
The xUnit family of testing frameworks
JUnit evolution
Test cases and assertions in JUnit 4
NUnit evolution
Test cases and assertions in NUnit 2
Organising test cases

Testing Approach
Testing sensibility: passive, reactive, active
Plain Ol' Unit Testing (POUT)
Defect-Driven Testing (DDT)
Test-Driven Development
Key TDD practices
The test-first cycle
Definition of done

More GUTs
Cohesive and focused tests
Propositional test names
Example-based tests
Choosing example data
Quality of failure
What to include and exclude
Short test cases
Single level of abstraction
Anatomy of a test case (Given-When-Then)

Listening to Your Tests
Feedback from testing
Reasons testing can be hard
Technical debt
Classifying and reacting to technical debt
White-box testing issues
Coverage

Refactoring
Kinds of changes to code
Code smells
Dimensions of change
Elements of refactoring
Some common refactorings
Refactoring motivation and applicability

Test-Driven Decoupling
Unit testability and coupling
Unmanaged dependencies
External dependencies
Unit versus integration tests
Characterising testability
Singletons and statics
Test doubles
Mock object frameworks