Appium has quickly become one of the most prominent test automation framework for mobile app, game and web testing. As an open source test automation framework, it drives Android and iOS apps, regardless of native, hybrid or mobile web apps, using the WebDriver protocol.
Reserve your seat now and mark your calendar! Our next webinar will go through how you can leverage test automation frameworks to test mobile applications built with react native. The webinar will include a Q&A session at the end so join us to ask our expert about how to adopt test automation for your react native apps.
As in today’s digital world, mobile apps are dominating human being’s daily lives, from banking to eating to traveling. It’s no secret that mobile is taking over web in the foreseeable future and that a mobile app is a must and ideal access point for servicing customers.
Bitbar will exhibit at IBC 2016 in RAI Amsterdam during Sep. 9th to 13th with an array of our latest mobile app testing solutions and our thoughts on how to consolidate mobile strategy for business. IBC is the premier annual trade show held in September for professionals engaged in media and entertainment, content creation and technical associations around the world. As the first time exhibitor, we will be presenting us at IBC Launch Pad at Hall 9. Come to visit our booth at 9.LP28 if you are also attending the conference and we would look forward to having a face-to-face talk with you about your current and future mobile plans.
Behaviour-Driven Development (BDD) gathers supporters for many obvious reasons as it is readable (by everyone), understandable (across teams and functions) and accountable (metric-driven for success/failures). Cucumber is a great example of optimized tool/framework to create such tests. This allows basically anyone (developers, QA, testers etc.) to write specifications in any spoken language that then gets executed as automated tests against mobile app(s). Furthermore, this sort of BDD approach incorporates the main standards of test-driven development (TDD) and provides a shared view and process for collaboration between all stakeholders.
Let’s look how to setup Cucumber and how to combine it for some standard test automation frameworks (Appium / Selenium).
More and more netizens rely on mobile devices rather than desktops to do searches, look for services and do shoppings while they are on the go. And many of today’s mobile apps utilize Internet browsers and web technologies.
Just earlier this week, Google announced the new Android N Developer Preview. The entire ecosystem is eager to hear what next alphabet – Android N – will be eventually called. But more importantly, there are tons of great new features, enhancements and promise of something great becoming finally available through this Android N release. The official version of Android N is estimated to be available during Q3’2016.
Few weeks ago Google announced in their blog that they have open sourced their internal iOS test automation framework called EarlGrey. As this is used internally with Google’s functional app testing and for example YouTube, Calendar, Photos, Play Music and some others are getting tested using this framework. Naturally, we have tested this framework out and it seems an interesting choice as a test automation framework suitable for several types of apps as well. There are lots of similarities between EarlGrey for iOS and Espresso for Android so let’s have a glance on what EarlGrey really is about.
One of the cornerstones in mobile app testing is the efficient use of test automation, with real hardware, making all that to work for you efficiently, and seamlessly integrate with your development and testing process. You know, the whole beef with test automation is that you can simultaneously run tests on different devices, preferably tens or even hundreds of those, to get comprehensive understanding of real behavior of your app on real platform. As discussed, there are myriad of different combinations when you consider OS version, hardware setup with all its diversity, networks, user conditions and many other things. Running something in concurrent – or parallel – mode will get you great details how things actually perform. Let’s take a look at some fundamentals of mobile app testing and how to use parallelism / concurrency to deliver you a significant value.
It was roughly a year ago when Facebook announced their intention to open source the React Native framework for building native apps. This wasn’t a big surprise considering their own experiences with the HTML5 based application which got lots of negative feedback. Moving to native was clearly the right move and as they had some good and popular implementation for writing web apps (with React) there was a need to bridge the gap between the native and web/hybrid apps. With this combo, writing native apps for mobile platforms (Android and iOS) is actually very easy and it seems to work well across different setups. But, how to test – and automate the testing of these sort of apps? We’ll take a look at this topic in this blog.