Last year, Apple CEO Tim Cook expressed the growing need to make all types of applications – web and mobile – accessible to everyone: “We’ve always viewed accessibility as a human right, and just like human rights are for everyone, we want our products to be accessible to everyone.” ~Tim Cook Websites frequently have been targets of disability discrimination and, unfortunately, this trend is making its way into the domain of mobile applications. [
Over the last year, there has been a growing trend of iOS development teams adopting XCUITest and additional frameworks built on top of the XCTest interface. Development teams have started to adopt XCUITest to get fast and reliable feedback. There are a few clear drivers to this growing adoption: Intuitive – Using XCUITest is quite intuitive for developers as it runs from within the XCode IDE Fast – Test execution against iOS devices is faster than any other UI test automation tool due to the framework architecture
In the past year, we have seen a huge increase in the numbers of customers adopting the Espresso and XCUITest automation frameworks. There are many reasons we’re seeing this growth. Much of it can be attributed to the inexorable trend towards DevOps; these frameworks also successfully address some of the long-standing challenges for traditional test tools.
The adoption of DevOps methodology has increased and the need to release to production in shorter cycles is driving teams to accelerate process and embed early test automation. Teams operating in this release velocity need fast & reliable feedback for every code change to ensure app quality. Is this new process forcing teams to choose between automation frameworks? Espresso (Android) and XCUITest (iOS) are UI automation frameworks that fit very well with this new development
Development teams today in many cases become THE business. More and more organizations build their business strategy on digital channels – Web, mobile and social. Although developers spend most of their day in their IDE, developing new code and debugging – in many cases, those few development teams are responsible for hundreds of millions in company revenue. To address business needs, development teams need to move fast and be more agile, they need to be
Many organizations are adopting agile practices to speed up their development pace and release apps to production in shorter cycles. But in many cases, especially in large organizations, the continuous integration testing activity is still performed by a centralized QA team late in the development cycle. This makes it hard to thoroughly test the "true" digital experience, even if there is significant test automation in place, and still have enough time to fix issues before
If you're an Android developer, you're probably familiar with Google's Espresso test automation framework. As an open-source tool, it's very easy for developers to use and extend within their working environment (Android Studio IDE). But before discussing the benefits of Espresso, let's understand the motivations and pains developers and test automation engineers face today while trying to validate their Android application (APK) throughout the build/dev/test workflow. Each build needs to be validated after code changes