The implemented project and its owners
REA Group published an account of an eleven-week Android testing experiment in its customer-facing Ignite app. This article is an independent analysis of that external engineering work. REA Group conducted the experiment; XIVTech does not claim involvement, a client relationship or ownership of the implementation. The primary source is Swapnil Gupta's REA engineering account, published 19 June 2026.
The relevant DevOps question is not whether AI can operate a screen in a demonstration. It is whether a test can run in the delivery environment, detect the intended failure and leave enough evidence for an engineer to act on the result. This connects the saved CI/CD and automation research to a real implementation without treating article-reading intent as a commercial service keyword.
What REA actually connected
According to REA's account, the team connected Buildkite and a Docker-based job to a Genymotion Cloud device through SSH and ADB. The job installed the application, ran Android Journeys and collected diagnostic output. REA describes direct device access as an important constraint in that experiment and reports that its attempted managed-device alternatives did not provide the access it needed. These are observations about that setup and product version, not a current universal compatibility claim.
For another team, the transferable decision is to verify execution prerequisites before expanding test coverage: device access, authentication, application state, output collection and the owner of each dependency. Google maintains Android Journeys documentation; consult the current requirements rather than copying historical configuration blindly.