Tests? Who’s got time for that? They slow us down. Test code should be an investment and not a cost. Instead, it is often treated as a mere annoyance and impediment to our progress. What does a good test code look like? One that will not annoy us and slow us down? One that will help us write, read and understand our code? How can we invest and collect interest from it instead of paying a price? This is not a theoretical talk. We will see how we can achieve this by example, using the common tools, libraries, and techniques available to us in the JVM ecosystem.
Where and when?