Is Calabash on life support?…. Some thoughts on our beloved framework, and a memoir on BDD and what you need to start thinking about.
With the proliferation of iOS devices year over year, the threshold of iOS success is higher than ever before. More companies like startups and SMEs find it not financially sustainable to acquire every piece of iOS devices with different OS versions and HW specs. On the other way, testing apps or games manually is not anymore an ideal option for QA process due to low efficiency and scalability issue.
Calabash is a test automation framework that enables mobile developers and pretty much anyone without coding skills to create and execute automated acceptance tests for Android and iOS apps. Calabash works by enabling automatic UI interactions within an application such as pressing buttons, inputting text, validating responses, etc.
In the past few blogs about Calabash for Android and iOS we’ve covered how to setup and get started with both platforms and define some of the fundamental things in Calabash. This time we’ll take a look at Calabash Steps, Step definitions and predefined steps that are set be default with Calabash installations. There are few tips and tricks that can be extremely handy and useful when it comes to using additional tools to help creating Calabash test scripts for your mobile app – and inspecting what should be put in Ruby code.
We walked through the basic setup and installation of Calabash for Android and iOS in previous blog, and this time we’ll take a look how you can build Calabash tests for your mobile application. If you have followed the example showcased in How to Setup and Get Started with Calabash you have properly generated the file structure for your first Calabash tests on Android and iOS. There are lots of difference (best) practices of how to create your Calabash tests, and we’ll use an example of basis to illustrate how these can test templates can be generated and further developed.
Calabash is quite popular choice for test automation framework and works fairly well with both Android and iOS. One of the greatest things with Calabash is that tests work seamlessly on both platforms if your application is identical. As this is not always the case you might need to break down test scripts for both platforms and we’ll take a look what it means and how to support both major platforms with your Calabash tests.
In this blog, I’ll walk you through of very basic setup, installations and how to get started with Calabash.
Mobile test automation genre is constantly evolving and new frameworks have been appearing for every specific need. As we’ve been supporting – and covering at our mobile app testing blog – all mainstream test automation frameworks here at Testdroid, we’ve learnt 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 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!
When it comes to test automation frameworks for mobile development there are bunch of great options for modern app developers out there. Many of these mobile-centric test automation frameworks are actively developed and have an active community around those. We at Bitbar believe in these communities and encourage everyone to contribute and use these great open source frameworks, as testing of your mobile apps, games and web-related stuff is really vital for your success. Naturally, all these frameworks have their own traits, pros and cons, and one of the top feature/benefit you should look from these frameworks is how well it exposes the issues, performance, problems and all that DNA to fix app for perfect user experience.
Like in all software projects, products and companies, the process of writing down documentation about requirements sparks never-ending debate of how it should be done, how much is enough, what and how certain feature requests and requirements should be documented. We are no exception here at Bitbar.
In this blog, I’d like to explain how we have approached this challenge, what have been the pit-falls for us, and how we have overcome of those issues. It’s just not about documenting requirements and specifications, but how to get those in our every-day doing and make these our strength – and build incrementally better product and the requirements documentation.
Thank you for being with us at Testdroid Blog. We hope you all had a great holiday and New Year.
When we look back in 2015, we have had fruitful technical innovations that enable us to maintain the market leadership. We’ve also shared plenty of thoughts regarding mobile app development and testing. Today, we would like to wrap up all the blogs in the last year and let’s review the top 10 of them.