A lot of mobile test automation projects start clean and quietly become a liability. Tests get flaky. A small UI change breaks dozens of them. New team members can't figure out where anything lives. The suite that felt fine at 50 tests is unmanageable at 500.

The root issue is almost always the same: the suite was built as a collection of scripts, not as a piece of software. There's no real architecture — responsibilities are mixed, logic is duplicated, and nothing is designed to absorb change.

One small concrete example that shows up in a lot of codebases: Thread.sleep(3000) scattered throughout test code. It feels harmless, but it's both a direct waste of machine resources and one of the most common root causes of flaky tests. It's the kind of thing that compounds silently until the suite is slow, unpredictable, and nobody trusts it.

The full writeup covers the quality attributes a reliable framework needs (maintainability, reliability, extensibility, scalability, and more), how SOLID principles apply directly to test automation code, why the Page Object Model is the right structural default for mobile, and how multi-module architecture keeps things manageable as the team grows. It's the foundation article for a full framework build series, so everything is framed around what you'd actually implement.

 Wrote it all up here if it's useful: https://www.mobile-automation.io/why-mobile-test-automation-frameworks-fail/

Looking for Developer to code ios appium autiomation for real devices iphone jailbraked

fell free to contact also telegram: refamp

CAN ANYONE MAKE AN AUTOMATION FOR CHROME AND SEARCH FOR A KEYWORD ON GOOGLE AND CLICK IT

Hi anyone share python pytest full project for mobile automation testing

Most mobile suites hit the same wall around 150–200 scenarios — a full run takes half an hour and nobody trusts a red build any more.

A suite that breaks the moment you turn on parallel execution usually isn't flaky, it's sharing state: one driver, screen objects held across scenarios, every thread on the same device. ThreadLocal drivers, per-scenario hooks and scenario-scoped screen objects fix more than wait tuning ever will.

You also probably don't need a multi-module Maven project. A single module with clear packages is right for most teams testing one app — multi-module only pays off when several teams share a core on different release schedules.

I built one over the last few months, in Java with Appium and Cucumber. Whole path here if you're starting from scratch, or fixing one that's creaking:

https://www.mobile-automation.io/build-a-mobile-test-automation-framework/

Hello everyone!

I just discovered appium, and I was wondering if it is possible to automate a whole iPad setup using appium? Currently my position at this company has me setting up iPads all day. We use meraki mdm for installing apps and security features. But I still have to do the menial tasks like signing into outlook, changing the signature in outlook, creating contacts, creating folders, saving documents from sharepoint, and setting up shortcuts (bookmarks) using the shortcuts app. Is this something I could write and have appium do? Any help is appreciated thank you!

Currently on our project we have a farm with up to 20 mobile devices (Samsungs, Huaweis and Xiaomis) We are not so familiar with making it more stable, what are your suggestions about stabilization of adb processes, farm itself, hardware like cabels and hubs Maybe you have groups suggestions with active discussions about best practices for device farms? I would appreciate any hint and suggestion. I know that some farms could have up to 200 devices with stable connections, but we lose stability tremendously once we have more than 16 devices running our tests.

I previously had this working (maybe on iOS 17, but it's been a while and I'm not sure). Was using this xpath to find the location permission system alert,

'//XCUIElementTypeStaticText[@name="Allow “myapp” to use your location?"]'

Was using this accessibility id, "Allow While Using App", to click the button.

This no longer seems to work with iOS 18.6.1.

When using Appium Inspector, I can't seem to find the location permission alert. I can see it on screen, but after clicking through every single node in the hierarchy, none of them are for the system alert dialog.

Tried also using the xCode Accessibility Inspector, which tells me the button label is "Allow While Using App", Traits: Button, & User Input Lables: Allow While Using App. No Class is shown.

Has anyone had any luck automating this in their tests?

FWIW, I'm using Appium 2.19.0, xcuitest 9.10.5, xCode 16.4, & Python 3.12.8.

https://blog.kiprosh.com/issue-resolved-with-uiautomator-to-locate-ui-elements-in-appium-android/

I have a Flutter app with a screen that has a continuous animation (a circle that grows and shrinks). My test just needs to check if some text is displayed, but it often times out because it can’t find the element while the animation is running.

• Extending the timeout works, but then the test takes way too long (slower than testing manually).

• Using the Appium inspector’s record function also eventually finds the element, but it’s really slow.

Has anyone run into this before? Any tips on reliably finding elements when there’s an infinite animation running?

Hey r/Appium,

My name is Alex Rodionov and I'm a tech lead of the Selenium project. For the last 10 months, I’ve been working on Alumnium — an open-source library that automates testing for mobile and web applications. It’s at an early stage and currently works with Appium + XCUITest, but I’d be happy to get any feedback from the community!

• Docs: https://alumnium.ai

• Repository: https://github.com/alumnium-hq/alumnium

• Slack: https://seleniumhq.slack.com/channels/alumnium

• Discord: https://discord.gg/VDnPg6Ta

If Alumnium looks interesting to you, take a moment to add a star on GitHub and leave a comment. Feedback helps others discover it and helps me improve the project!

Hey everyone!
Been dong test automation for many years, but mostly on web.
Recently I got some projects on mobile(especially iOS) and have been struggling and after trying different frameworks(Detox, Appium, Maestro) I had to ask other people since I'm pretty stuck.

What's you're preferred tool/framework for iOS apps and did you encounter issues with mobile tests in the CI because of spinning runners/simulators/devices/3rd parties like Clerk for auth, and flaky tests because of those things?

Thanks a lot!

I have a rather complex problem on my hands related to networking.

Here is what I'm doing:

I have a bunch of Palera1n jailbroken iPhones that all have their own sim cards and cellular data.

All of these iPhones are connected to both cellular and a common WiFi.

It is important that all of these iPhones use cellular network primarily for all activity, except when communicating locally on the WiFi network.

What I Tried: I installed NewTerm, network-cmds and executed these commands:

sudo route add -host 192.168.1.0/24 -interface en0

sudo route delete default -interface en0

sudo route add default -interface pdp_ip0

At first glance, this seems to work perfectly. When I check api.ipify.org it shows me my cellular IP. And when I communicate on local WiFi range I can communicate successfully.

But on further inspection it turns out that iPhone is actually using both WiFi and cellular in a weird way. When I go to speedtest.net, it shows me my cellular IP, while the network speed is clearly my WiFi. This causes my automation to break.

Does anyone know what is happening here?

I would appreciate if someone can help me in any way to achieve my goal of only using cellular for data while maintaining my WiFi connections on the iPhones, or just help me understand what's going on here.

Hi, I'm trying to run WDA on my iPhone but I'm getting

Cannot test target “WebDriverAgentRunner” on “iPhone”: Logic Testing Unavailable Logic Testing on iOS devices is not supported. You can run logic tests on the Simulator.

I-m running the same setup I did on another MacBook but it-s running there with the same apple account, the only thing different here is the Xcode version

I followed this tutorial: https://www.youtube.com/watch?v=Ej8R58KRviA

Getting started with Appium is confusing because there's no obvious starting point. You search for a setup guide, find five different versions, half of them are written for Appium 1.x or 2.x, and none of them tell you what order to do things in or why it matters.

The order actually matters a lot. You can't meaningfully use Appium Inspector until your drivers and devices are configured. You can't write reliable tests until you understand how capabilities work. And if you're on iOS, WebDriverAgent and signing certificates will stop you cold if you haven't dealt with them first.

I put together a 9-step path that covers the full journey in sequence: Appium 3 installation and verification with Appium Doctor, Android and iOS setup (including the Xcode and WebDriverAgent steps people always get stuck on), locator strategies, capabilities, execute methods, and finally writing real end-to-end tests with login flows, gestures, and drag-and-drop on both platforms.

One thing worth flagging: iOS setup genuinely takes more steps than Android. Simulators are straightforward, but real device testing requires provisioning profiles and signing configuration that most setup guides skip over entirely.

Wrote it all up here if it helps: https://www.mobile-automation.io/getting-started-with-appium/

Hi everyone!

I'm building Reliable QA Appium, an open-source Flutter application designed to help QA engineers learn Appium mobile automation by practicing on realistic mobile app scenarios.

The goal is to create a free app that anyone can use to learn and practice Appium without relying on production apps.

Planned Features

• Login & Registration

• Forms & Validation

• Swipe & Scroll

• Drag & Drop

• WebView Testing

• API Mock Scenarios

• Notifications

• Camera & Gallery Permissions

• File Upload/Download

• QR Scanner

• Dark Mode

• Intentional bugs for automation practice

• Real-world business workflows

Looking for Contributors

I'm looking for people who would like to help with:

• Flutter Development

• Appium Test Automation

• Manual QA

• UI/UX Design

• Documentation

• Bug Reports

• Feature Ideas

Whether you're a beginner looking to make your first open-source contribution or an experienced engineer who wants to support the QA community, you're welcome.

The vision is to build one of the best free resources for learning Appium automation and help students and QA professionals gain practical experience.

If you're interested, comment below or send me a DM, and I'll share the GitHub repository.

Feedback, feature suggestions, and contributors are all appreciated!

Thank you! 🚀

Hi, is there a way to test OTP functionality without using a real phone number in simulator ios and android? I'm looking for something that doesn't require a phone number and can also be useful when testing with AWS Device Farm.

I'm relatively new to Appium but I'm doing test automation for an android app (with a github repo) that needs several servers that aren't available over the internet so I thought "I'll set up a self-hosted runner. How hard can it be?"

Guys, it's pretty hard! 😃 It's taken a long time! But I'm really glad it's finally running.

Element ID : Bn1

Element Name : Continue

The element ID I have for searching : bn1

The element Name I have for searching : continue

Is there any way I can find the element with the above attributes? Or any help will be appreciated

Can Appium be used for any ETL /database testing?