One of the requirements of using Appium for mobile test automation is to start the Appium server in the background so that it can listen to the requests from the mobile app under test. And there are multiple ways that we can install and start the Appium server in the background.
As Appium is a popular framework for cross-platform app testing, many platforms provide the Appium Server-Side execution to help improve test efficiency. But Appium Client-Side execution also plays a critical role for many teams to validate Appium tests for specific reasons. And what makes Bitbar Cloud stand out is that our platform is one of few mobile device testing clouds that has support for Appium Client-Side execution. And we’ve taken its capabilities further –
testdroid_multiSessionWait is now available.
My Background: Appium and Mobile Game Test Automation
Before going into details, I’d like to share a bit about my own context and the struggles I’ve had in mobile game test automation.
2017 was another exciting year for Bitbar. We introduced powerful new features and teamed up with new partners to strengthen our mobile DevOps platform. ‘Speed’ is the single word to be used to wrap up the achievements for the year. We want to take this opportunity to have an annual review.
We are excited to bring you the news that iOS 11 devices are available for iOS test automation on Bitbar Cloud. It’s time to incorporate more iPhones and iPads in your device list for iOS app testing that enlarges your test coverage and improves your confidence before shipping your iOS applications to end users. Sign up now and check if your apps work on iOS 11 devices.
At Bitbar, we always push the boundaries of agility and quality by providing organizations with the most stable and scalable testing solution for mobile apps. In order to bring you the best iOS development and testing experience, we will perform an iOS environment upgrade and add iOS 11 devices to our Cloud on September 13th.
Happy Summer! Sadly there are about 6 weeks left till autumn 🙁
Last month we heard about iOS 11 and boy there were some good announcements! By now most of you know that when WWDC rolls around it’s a scramble to make sure your team is prepared for the changes in iOS app development and testing. Today I wanted to highlight some of the big changes that are coming and how they will probably influence your iOS app development and testing.
We’ve talked about this quite many times here at Bitbar Blog, but Appium has been one of the most solid open source test automation frameworks during the few past years. And despite of significant changes in Appium iOS, it seems that this framework is going (again) full steam ahead.
The latest addition is the Appium Desktop tool that enables users to work with Appium on their desktops and use Inspector for yet better analysis of their app. Let’s take a look at how to get Appium Desktop installed and how to work with it.
We’ve been seeing a lot of talk from users on Appium regarding the changes that have come out of the Appium 1.6.0 release. One of the biggest changes are the Appium inspector missing with Appium.
We’ve done a lot of research and we wanted to provide you the options that are available to work around this issue.
One of the tools that’s available that we use internally here on projects is Macaca.
It’s quite common in mobile app testing that application and test script with a test session needs an access to various locations. For example, some test scripts need to access URLs, databases, back-end servers or even App Stores (e.g. Google Play or Apple App Store). With the access, test session can get, download or update certain applications from app stores before the actual test session will begin.
In this blog, we’ll take a look of how Appium test script can access Apple App Store and how to use certain XCUIElement components to assist your script with that.