Solving the problems of Espresso Android autotests in the real world
Alexey Turin will tell how certain problems in UI testing automation of Android application are solved without architecture reworking and revision for autotests.
Very often the projects that have already gained the course and have a large codebase conclude that you need to write autotests. Including the UI autotests. In this situation, you don’t have the opportunity to remake the architecture for tests. As a result, tests became unstable and distract the product development team more than they help it.
In his talk Andrey will tell:
how to lower the threshold to project participants tests;
how to build simple and clear UI autotests architecture;
how to make tests stable without changing application architecture and how to deal with emerging flaky tests;
how to implement the solution in CI and build a reporting system that everyone will understand.
All solutions will be shown on the example of a specific demo application. This application you can see on GitHub. People can use ready-made solutions in their work.
The purpose of the talk: to show people how certain problems in UI testing automation of Android application are solved (case by case). These solutions don’t require reworking the application architecture or any significant revision for autotests.