There’s no doubt that quality is becoming a joint team responsibility, and with that in mind it is not enough for traditional QA engineers to develop and execute test automation post a successful build. Expectations around mobile application development teams are growing; they are on the hook to produce quality code. To do this, devs must try to include as many tests as they can in their build cycles for each code commit. Tests can be either unit, functional, UI or even small scale performance tests. With that in mind, dev teams need a stable environment that allows them to perform these quality-related activities easily, so they deliver better code faster!
Mobile Application Development Challenges Today
According to the mobile app devs I’ve worked with, common challenges they face in the workplace today include:
- Solving issues that come from production or from QA teams that require a specific device and/or environments that are usually not readily accessible for the dev teams
- Validation of newly developed apps or features across different operating systems and devices as part of their dev process
- Lack of shared assets for the entire dev team, preventing it from getting a “long USB cable” that enables full remote device capabilities and debugging
To help solve these issues, the recent 9.4 release of Perfecto’s Continuous Quality Lab takes a significant step toward helping developers accomplish more tests as part of the build cycle. By considering the above challenges and requirements, 9.4 enables developers to get enhanced remote access to mobile devices in the cloud and perform any operation that they could have done with these devices if they were locally connected – like debugging, running unit tests, testing UI at scale from within the IDE and more.
In addition, when referring to Android development activities, it’s clear that Android Studio and IntelliJ IDEA are the leading IDEs to operate in. For that, Perfecto built a robust plugin that integrates nicely into the mobile application development workflow.
9.4 and Espresso Framework
There’s no doubt that developers are adopting Espresso more and more, and for various reasons like:
- Embedding Espresso into Android Studio plays an important role for Android developers
- It’s very fast and easy to execute and receive feedback on Android devices
Espresso can be used within the Continuous Quality Lab in the following 2 modes:
- Locally (see below)
- Via Continuous Integration (CI) using a command for Espresso test execution through the Jenkins server
To see this in action, check out the video that demonstrates how to get started with remote access to devs using the Continuous Quality Lab within Android Studio with Espresso for testing and debugging purposes.