- but you MUST access UI only through it! • Use IdleResources to tell Espresso when the UI is in a stable state. • Disable animations via ADB before running tests to avoid flakiness. • Write your own ViewMatchers when required, DO NOT attempt to access UI elements from testing thread!
Emulator startup is painful - with both emulators • You need to clean up code! • You MUST disable animations or things WILL fail. • You’ll need a running UI session for Genymotion.
Features and changes are reviewed by another person. • No merging before “8 green ticks” or confirmed flakey test. • Master isn’t touched directly. • Bugs get their own tests together with fixes. • Master branch is available to customers as a nightly.
maintenance. • Jenkins nodes require even more maintenance. • Both iOS and Android UI frameworks are flaky. • Whole team must invest in testing… • … and accept that you’ll lose time kicking your CI into obedience.