As a developer, most of the time, you are being focused on solving concrete problems. This process get’s all your attention on implementation details to make it just work. If time persists you might spend some time on writing tests for your code, but not going far into details on all the edge cases. It is very hard to verify your own creation in all possible ways. Stepping out of comfort zone and think like a consumer is what test engineers are good at, thinking from the end. During this session I’m going to share my daily tricks on how to help developers writing better tests which leads to less bugs and more testable architecture.

1. Andrii Dzynia
Software Engineer in Quality
@adzynia
Exploring your unit
tests

2. 2
Spotify brings you the right music for
every moment!
Over 20,000 songs added every day
Started in 2006 (in Sweden)
Now 1500+ employees, 600+ engineers
5(STO, GBG, NYC, BOS, SF) engineering offices
Over 30 million songs available
Over 60 million active users
Over 15 million paying subscribers

3. What is exploration?
3

4. 4
Look for inspiration
Prepare a model
Focus/de-focus
How are you exploring the
system?

5. Let’s explore.
5

6. Why exploring source code
is useful?
6
Learn how system is actually works
Find new ideas to what can be tested
Fast test execution

7. Outcome
You are learning
Extending unit test suite
on the go
Biased view on a system
Does not save you from
bugs on a system level
7

8. 8
Take Aways
Check out your system source code(if you have not done
already)
Pair up with a developer to get high-level overview
Start exploring the source code in order to learn more
about a system

9. 9
@adzynia
adzynia@spotify.com
Spotify Engineering Culture
part 1
part 2

10. Check out http://www.spotify.com/jobs or
@Spotifyjobs for more information
Want to join the band?
Follow @SpotifyEng on Twitter.