So far we have covered most of the topics around setting up XCUITest framework and making it scalable and maintainable. However, we haven’t covered the XCUITest API and the other features of XCUITest framework that we can use in our iOS app testing. In this post, we will cover the basics of XCUITest API and how to utilize those API to write UI tests for iOS apps.
As many of you probably know Robotium was one of the first mobile test automation frameworks that was supported by Testdroid products. In addition, many of you have started with and actually got the first touch in mobile test automation using this framework, we’re honored to announce that Robotium Extension Solo library – also known as Robotium ExtSolo – is now open source and fully available at Github.
As a mobile app developer, it doesn’t mean that your job is done when the app gets developed. One of the following questions in front of you is user engagement; put it in a simple way – install, usage, and stay.
In any business, customer acquisition is the first challenge to tackle, but a more daunting task to companies is improving customer retention and lower customer churn rate. This philosophy also applies to mobile apps – Getting the initial app install from the competition is important, but keeping users satisfied and your app installed is more critical.
Speaking of mobile game testing, it is a common misconception that manual testing is the only way to go forward. In many cases, it is the first thing to start with, but to really get all issues spotted out and fixed before the game is published, test automation built into the process, hammering each and every regression and advancement can yield significant results when considering the customer-ready game.
Every dog has its day and in this case, every blog too. We decided the last blog in our well-read series, Deconstructing Mobile Testing Methods, would end with the list of all lists and would be your raison d’etre or making money and getting those 100M plus downloads on your app.
So far we covered The Pros and Cons of Different Mobile Testing Methods, Using Twitter App as an Example: How to Build Robust and Reliable Automated Tests, our most popular in the series, Advanced Automated Testing as Part of Your Development Work, Goodbye Hand-Written Test Cases! and now our crowning jewel, Getting The Best Out of Today’s Android Testing Tools.
The Google Play has become an overwhelming distribution channel for developers building their next-big-things, either in forms of applications, games or even services. This ever-expanding marketplace gives developers a global reach and target coverage of hundreds of different Android devices on a rapidly growing and changing platform.
However, due to a variety of Android OS/platform versions, fragmentation does exist. Android fragmentation is known to cause multiple and incompatible versions of the system specific to the OEM and that causes applications and games to work differently (or wrongly) on many Android devices.
The new version of Testdroid Recorder with magical number 1.1.11 is now available for download.
Testdroid Recorder has truly cemented its place in Android testing tools market and we can safely say that Testdroid is the most comprehensive Android testing solution around. However, we at Bitbar don’t stop here as our goal is to even accelerate our rate of innovation and improve the end to end solution even further.
We are proud to announce that Testdroid Recorder is now officially out from Beta. The production version includes numerous new features, usability improvements and a lot of bug fixes.
The feature highlights of Testdroid Recorder 1.0 are:
The new 0.9.12.alpha version of Testdroid Recorder is out! We worked hard to provide you new features and improve the existing ones. The enhanced GUI simplifies the recording. Now you can pause and resume it without restarting the recorded application. It is also possible to remove the recorded commands just during recording.
How to design Android application which get you more money? Do you know where money comes from? It comes from really good users feelings and experience. You should know that if your app does something that is useful but ugly, slow and confusing, people will not use it. If your app crashes, it won’t be featured. If it doesn’t have good usability and quality, you have really failed as a developer.