A couple of days ago, I had a conversation about Android tests on Twitter. I would leave it here a note.
The conversation was:
- How to run UI tests in order
- Is there any good way to make them stable?
- How to get a system dialogue via Espresso?
We discussed:
- It’s better to use RuleChain to handle the order than use FixMethodOrfer since the FixMethodOrfer might break in sharding or parallel running case
- Put all steps into one method if the steps are one scenario by them
- We can restrict a number of UI flow switching UI flow based tests with activity based one using asserting intent so that we can reduce transition from a view to another. https://www.slideshare.net/KazuMatsu/cookpadtechcond2018mobiletestautomation/75
- We need to use uiautomator when we’d like to get the state. But if we should handle it many times, the advantage of Espresso decreases…
~ my tech diary ~ 