The goal is to learn to write stable tests for a Hexagonal Architecture. This kind of tests change as little as possible during refactorings or redesigns. The only trigger to add or change a test is a new requirement.

It is often the case that the tests are too tightly coupled to the implementation of an application. It then becomes harder to refactor or redesign parts of an application. This pain leads to a design that is harder to change over time.

We’ll explore a more robust way to write tests that don’t stand in the way of refactoring.

Be prepared to write code.

The examples will be in Java and C#.

Technical Agile Coach Twitter LinkedIn

Michel Grootjans has been programming since the age of 12. He has programmed strange machines like the TI 99-4A, the Atari 2600, Mac128, HP28, Apple II, Siemens PLC’s, using languages like Basic, Pascal, C, HyperTalk, Assembler, … along the way.

His professional experiences include building enterprise applications for media, government, chemical plants, telecom, HR, insurance, … in javascript, C#, java and, ruby.

He helps teams with continuous improvement, focusing on outcomes over output.