In my previous post, I examined where goal-based agentic testing fits within the mobile automation pyramid. The conclusion was simple: it doesn’t replace traditional UI automation; it complements it.
Goal-based agentic testing introduces a new layer within the automation pyramid, prompting questions about its precise placement.
Testing mobile applications has always been a bit messy.
Traditional automation provides us with scripted steps. Tap here, type there, check this, and we execute those steps repeatedly. It works… until it doesn’t.
A release train, a regular cadence for shipping software, is one of those ideas that sounds good in principle. Ship often. Ship reliably. Reduce stress.
Shift-left testing in Mobile Application Development sounds simple. Test earlier, find bugs sooner, release faster.
I haven’t blogged lately and wanted to get one finished before the end of the year. So I decided to write a blog post about Android Debug Bridge (ADB) which I learnt more about at droidcon London in October.
Working on an Android app that requires internet permission?
My 2020 article on the challenges of mobile app testing has been revised to incorporate information on remote work. The original article can be found here. The emergence of remote work has introduced a fresh set of obstacles to mobile app testing.
To get started with Ruby and Selenium WebDriver, there are a few essential commands you should know. Here are some of the most important ones:
Reflecting on my album cover flow. I wanted to make the UI a bit more interesting
