Software Development is a creative activity that requires focus. During coding session you as a programmer tends to make so many decision that sometimes force you to neglect 'unimportant details' that might sounds like specific use cases, unclear statements or somethings that won't gonna happen. In most cases the system even so complex that is not that easy to step out and see the whole picture, even from user's point of view. Historically software developers used to trust other people called testers to verify those 'details' from user's perspective before deploying into production. In order to have proper alignment inside the team dedicated 'QA step' added to the process. That obvious solution have some quick-wins with outcome of found bugs before releasing the software. But there are some tradeoffs, such as: slower delivery cycle, extra test documentation and GUI automated tests that are not that easy to maintain. During my talk I would like to share some insight and lessons we learned @ Spotify that helps us improving team's development productivity without losing quality of the product. Hopefully that will help your team as well or at least show one of the directions you might want to follow. Spotify Engineering Culture: https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/ https://labs.spotify.com/2014/09/20/spotify-engineering-culture-part-2/

1. November 30, 2015
Applying testing mindset
to software development
Andrii Dzynia
Software Engineer
@adzynia

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. 3

4. Organic Structure
4
Scaled Agile @ Spotify@joakimsunden

5. 5
Is a Programmer
Enjoying learning new things
Passioned about technologies
PETER

6. ONE DAY OF PETER’S LIFE
WAKE UP
THINK ABOUT PROBLEM WAS NOT ABLE TO
SOLVE YESTERDAY
COMMUTE TO THE OFFICE
SYNC MEETING WITH A TEAM
FINISH CODING AND DEPLOYMENT
GO ON MEETING
GET NEW TASK TO WORK ON
START IMPLEMENTATION
GO ON MEETING
GO HOME
6

7. WHERE IS THE HIDDEN RISK?
7
@visbeek

8. Peter deployed the code.
Bug
NullPointerException
Issue
403
5xx
503
4xx
IllegalStateException
Bug

9. 9
Let’s hire a tester!

10. Scenario A
Testing is not my job attitude from programmers
Tester is full of boring routine work
Users are frustrated how long it takes to fix bugs
10

11. Scenario A'
‘Testing’ is boring let’s automate it attitude
Tester is helping out with test ideas
Tester establishing communication channels with the
users
11

12. Questions
How can we spot issues early?
How could we miss that bug?
How to fix missed bugs faster?
12

13. Think how to receive feedback
13

14. Feedback during meetings
14
challenge ideas and
solutions via healthy
discussions
prove hypnotises via end
user collaborations

15. 15
Feedback while online
comments, corrections,
suggestions
shared with everyone, any
input is valuable

16. Feedback during
implementation
16
write tests during implementation
rise your concerns during ad-hoc
discussions
peer review before merging to master

17. 17
Pre-merge feedback

18. Post-merge feedback
18

19. Safety nets
19
http://www.chinaplasticmesh.com/wiremeshimg/other/constructionsafetynet-3.jpg
http://boliplastic.en.ecplaza.net/1.jpg

20. 20
Testing becomes fun

21. Test(noun)
vs
Test(verb)
21

22. 22
Pre-merge process
Post-merge process

23. Testing uncovers
what your system/
product can and
cannot do.
23
@adzynia

24. If testing is not fun,
then something is
wrong.
24
@adzynia

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

26. http://www.spotify.com/jobs
We are hiring!