SPA Conference session: Scents of Tests: Finding Your Fragrance

One-line description:Different approaches to developer tests
 
Session format: Tutorial (75 mins) [read about the different session types]
 
Abstract:Three are dozens of different ways to implement developer tests for your software. You can test for state or for interactions. You can have lots of unit tests or you can go for integration tests. Or a mixture of both. There are also several patterns for structuring your tests. Which approach is best depends on the situation, of course. To be able to choose a course of action, we need to know about our options and understand their respective implications. In this session we will introduce several ways of implementing developer tests, talk about the pros and cons of each method, and introduce scenarios where to use them. The session is technical and consists mostly of code review. We encourage audience participation and won't have a closing Q&A in the end as it's going to be a packed presentation as it is - and bound to spur conversations throughout the session. Instead, the hosts will transition the session into a facilitated discussion towards the end of the session.
 
Audience background:* Java basics
* Unit testing basics
 
Benefits of participating:Through concrete examples we hope to give the participants new approaches for writing test code. Discussions on the advantages and disadvantages of the methods in different contexts. Our aim is that everyone leaves the session with at least one new idea on how to improve their tests.
 
Materials provided:
 
Process:Participants will review several different approaches for writing test code and discuss the pros and cons in small groups.
 
Detailed timetable:00:00 - 00:05 Introduction and objectives
00:05 - 00:50 Reviewing and comparing different test code approaches
00:50 - 01:15 Facilitated discussion
 
Outputs:
 
History:
 
Presenters
1. Sami Honkonen
Reaktor		 2. Lasse Koskela
Reaktor		 3.