"Oh... Now I see... I mean Integration tests between `modules`, while you mean between `components`" - Discovered after an hour-long discussion during Code Review. They need one more our to find out that integrating a `module` is very different from `component`. But first things first, let them discover first that they define a `module` and `component` in a different way. Then the tester says: Integration is when we connect `microservices` together...

Is that true that we can only develop unit, integration and E2E tests? Then what is the `unit`? And `Integration` - means we integrate what? Why not call it a `unit` too, since it is written in jUnit? Surely, the `Integration` is the one that is slow, `unit` is the fast one. Why actually they say we should separate Application Logic from Domain Logic, while we still cover it with the same type of Integration test?

In E2E System tests what are the `Ends`: classes, components, modules, microservices, contracts or the whole system? Do we even have components and modules inside? What can a tester do in such a case? To be safe and to keep chaos under control he resorts to duplicate test cases 'on his own'. He will use SIT with a fully running system to reach the seventh step in the form where he enters a first name that is... one char too long. Nothing better than an expensive test suite that is steadily red.

Ouch! Enough! Stop it, it hurts!

This is how it goes with testing. jUnit is simple, AssertJ as well, Mockito, even Spock. Just one tutorial to go. There we are with several tools. We miss guidelines on how to use them together to build confidence. It's worth picking one of the testing strategies. Wow... so we can have a strategy? And there's more than one to choose? Show us!

I will! But please leave behind your boundaries and prepare to embrace something new.

audience: For Developers and testers (Intermediate)
time: 30-60 min