E2E2U: Slack's Journey to Developer-driven End-to-end Testing

What you'll learn

Two years ago, the Slack team presented on an approach that makes authoring reliable Android UI tests easier. To date, Slack Android developers have written 637 UI tests and all of them run as part of a merge-blocking (and, most importantly, reliable) pull-request check. Having conquered this level, we set our sights on the top of our test pyramid - automated end to end tests. This test suite was still being maintained by a single hero developer, who, through sheer grit and determination, didn't let this important part of the release process die. Armed with experience in functional UI testing, Slack embarked on an adventure to make our end-to-end test suite a shared responsibility of the entire team. The team's journey has taken them through the fields of Dagger, the bog of Espresso IdlingResources, the inferno of ProGuard and, perhaps, the most challenging of them all, cultural aspects of quality assurance. Valera Zakharov looks forward to sharing where Slack is in their never-ending testing story.