Spotify Radio Desktop Client (Assumptions (A CI build is run every time…
Mac (latest 3)
Windows (latest 3)
Win XP (an exception to the 'latest 3' rule due
Customer satisfaction up/down?
How many users
are we reaching?
How deep are
What is the purpose of 'radio'?
Can we prove it is met (or not)?
The radio data matching algorithm is the same for free and premium customers
Radio requires internet connectivity (no offline access)
Company policy is that the latest 3 OS platforms are supported
Automated testing is in place in the form of the
A CI build is run every
time code is checked in to CI
Every developer runs their local tests before checking in code
UI tests are run with the build
Test your tests: Randomly alter an automated test and ensure it fails
The team is co-located and cross-skilled, including the Product Owner
The team has full access to other Spotify teams who own integrating components
such as personalisation/ data science
Other teams have tested their own code which therefore does not require component-testing (depth) by our (the radio) team
The UI has been prototyped, A/B-tested and refined
There is a rollback strategy in place
Highest priority functionality
Highest risk functionality