Mobile test automation genre is constantly evolving and new frameworks have been appearing for every specific need. As we’ve been supporting all mainstream test automation frameworks, we’ve learned quite a lot about how different frameworks work for different types of mobile apps. Appium has been in tremendous growth, but there is no reason to forget Calabash. Both of them provide a great foundation for cross-platform testing strategy and due to some concerns about Calabash and recent changes in the industry, we’d like to provide you a tutorial of best practices with Calabash, how to get started with it, how to combine Calabash approach across other frameworks, and some useful tips!
Last month I covered few topics on how we’re running our device farm and in that blog I sidelined briefly the built-in monitoring that provides us vital element to ensure everything is working as expected and users can get the best customer experience through the service. As there is a myriad of moving components, attributes, that all must be maintained and checked whether everything is up in speed, we have to rely on our internal monitoring implementation to keep everyone up-to-date with the status. Actually, this is not whole lot different thing if you are running your own device farm with Bitbar On-Premise as the tool provides some neat capabilities for monitoring test runs, queues, devices, infrastructure, capacities and so forth.