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!
This is the 22nd blog in our Things You Should Know About Appium blog series and this time we’ll be focusing on how to use image recognition when testing mobile apps, games and even websites. The image recognition has been lately one of the most prominent approaches for enabling test automation for mobile apps and games that have graphics content or other content that regular test automation frameworks may not be able to identify with IDs, description or object characters.
Just a few years ago, the process of mobile test automation was too immature and the entire mobile ecosystem wasn’t ready to adopt large scale test automation setups for mobile app testing. Furthermore, test automation wasn’t necessarily seen as possible to be done across devices, simultaneously, and in parallel mode. Nowadays, things are a whole lot different. Test automation, with frameworks like Appium, real devices, a variety of different hardware and using network connections and real back-ends intensify testing of Android and iOS apps.
This is the 21st blog in our Things Should Know About Appium – and we’ll go through a basic example of how to get Appium test started on available Android and/or iOS devices, just in seconds using device finder functionality.
In the previous blog we had a glance on to use different types of XPath locators in Appium and how those function calls work when building your test scripts. Today, we’re continuing with the same theme but this time we’ll focus more on Selenium WebElements and Appium MobileElements and how to use those to explore an ideal way to interact with UI elements. This is the 19th blog in our massive Things You Should Know About Appium blog series. Also, I’d like to thank many of you for providing such great feedback on our prior blogs.
As we’ve been discussing here at Appium Weekly blog, there are various different ways and tricks to locate elements in a web page. Appium – based on Selenium foundation – provides excellent methods to locate elements by using an XPath function. And in fact, there are lots of different XPath methods you can use, by name, ID, link texts, partial link text, tags, class names and some others. This is the eighteenth blog in our Things You Should Know About Appium – and now, let’s take a look at those different XPath tricks you might find useful.
We’ll be continuing the topic we discussed on our last Appium blog post on finding UI elements and this is the 17th blog in our series of Things You Should Know About Appium. This time we’ll be focusing on Selendroid and how UI element identification works with it. Just like Appium and uiautomator, Selendroid also comes with a useful inspector tool – Selendroid Inspector – which we will also take a look at in this post. And obviously, this applies only to Android.
It’s time to look at how different elements can be found with Appium and what actually happens on the background when Appium does most of the work for you. This is the 16th tip in our Things You Should Know About Appium and with the following blogs, I’ll be focusing more on Appium commands, how to use them effectively and what tricks may be involved. As always, I’ll provide some code examples for each and every (popular) programming language that is used with Appium.
This is the 15th blog in our Things You Should Know About Appium blog series. There are certain limitations that each framework and programming language have so this time around we’ll focus on how to break off from the limitations and how to use some conventional mechanisms during your test runs. For example Android Debugging Bridge (ADB) and how to use it in the context of Appium. Naturally, this is only available and usable with Android. More importantly, ADB is usable and actually very handy when used together with Appium and test runs on execution. This works well for testing native apps, but also with mobile games using image recognition. Furthermore, not only with Appium, but literally with any test automation framework you could use our image recognition method or dynamic scripting with real-time inspection of log data. Let’s dive deeper.
This is the 13th tip in our Things You Should Know About Appium blog series, and we’ll take a look what types of tools are used with Appium and what are the most important ones for you as well. Naturally, the right tools can make your life so much easier and enable you to get the best out of test automation and Appium. For example, Appium Inspector and some other tools are very handy when identifying some visual elements in your app. These tools have their limitations so we’ll also discuss how to tackle those.