This is Part 2 of an article on the mobile test automation practices we use at Bumble. In Part 1 we looked at the role of automation in our processes, gave details of the framework, and examined in detail three practices we employ when creating autotests.
Here in Part 2, we cover the following topics:
- Practice no. 4. Verification of element state transitions
- Practice no. 5. Guaranteed preconditions setup
- Practice no. 6. Simple and complex actions, or Independent steps in tests
- Practice no. 7. “Optional” elements verification (which is mandatory to do 🙂)
- Summary
- Bonus.
I would like to stress…
Bumble is the parent company that operates Badoo and Bumble, two of the world’s largest dating and connection apps with millions of customers worldwide. Delivering new functionality as fast as possible is a priority. However, it is important that the speed with which we work in no way compromises the quality of our apps.
Automation is a great help in that regard. The position of automated testing has changed a lot over the past two years. The number of people currently actively involved in test development has quadrupled from 10 to 40. And any new functionality in our applications now…
