I’ve only ever done mobile testing on a small scale myself (startup level). The site was built in React. We had decent logging so we could see the devices our users were accessing our site on. We had no mobile automation set up, my testing was mostly done manually with a few physical devices and browserstack. Oh, and we were deploying continuously to production.
When I was there, we were in talks to diversify and expand the product. This, of course, would eventually mean a larger software development team and hopefully a larger software testing team to meet the diversification demand. The hope was that the product could become a progressive web app. This wasn’t set in stone though but it was in discussions.
So, to my question(s):
- When is a good time to start thinking about mobile test automation?
- Have you ever had to scale mobile testing efforts? Either from a situation similar to above or for some other reason. If so, what helped you/your team to achieve this?
- How did/does the release cycle affect the scaling? E.g. continuous deployment vs deploying once per week or once per fortnight.
- When it comes to something like a progressive web app, how different is your approach to that vs a native app?