Question 1

What is RobotActions Device Farm?

Accepted Answer

RobotActions Device Farm is a cloud testing platform that gives you real Android and iOS devices, Apple TV and Google TV boxes, and real browsers, in our cloud. Reach them from your browser, drive them with Selenium, Appium, Playwright or WebdriverIO, or let an AI agent drive them over MCP.

Question 2

How many devices can I test on simultaneously?

Accepted Answer

Your concurrency is simply the number of devices on your plan: buy 11 devices and you can run 11 sessions at once. Sessions and test minutes on those devices are unlimited. A device is yours alone for the session and goes back to the pool when you release it; every device is restored to a clean state overnight. Enterprise plans get a dedicated host and devices that keep their state.

Question 3

Do you provide real devices or emulators?

Accepted Answer

Real physical devices, always — no emulators and no simulators. They behave differently from the hardware your users actually hold, which is the whole reason to use a device farm.

Question 4

What integrations do you support?

Accepted Answer

RobotActions works with Jenkins, GitHub Actions, GitLab CI/CD and other CI providers, and with Selenium, Appium, Playwright and WebdriverIO. Over MCP, an AI agent can also reach Jira, TestRail and Azure DevOps — reading stories and acceptance criteria, updating test cases and filing defects. Our API allows custom integrations with your existing workflow.

Question 5

Can I record my test sessions?

Accepted Answer

Yes, all test sessions can be recorded with our video playback feature. This allows you to review test executions, analyze failures, and share recordings with your team for collaborative debugging.

Question 6

Can I test geo-restricted applications?

Accepted Answer

Yes for location itself — you can emulate the device GPS position and mock API responses, so location-based features in your own app are fully testable on a real device. One limit worth stating plainly: we do not control the IP address your traffic leaves from, so a restriction a third party enforces by source IP is out of scope today.

Question 7

Can I test TV apps?

Accepted Answer

Yes. Apple TV (tvOS) and Google TV / Android TV boxes are in the device list alongside phones, at the same per-device price. Live control gives you a full remote in the browser — d-pad, OK, back, home, play/pause, volume, power, and typing straight into the TV — next to a live stream with audio as well as video, so you can check audio and playback, not just the screen. AI agents drive them over MCP, and Appium suites run on them the same way they run on a phone.

Question 8

Do live sessions include audio?

Accepted Answer

Yes. Live sessions stream audio as well as video on every device type — Android phones and tablets, iPhone and iPad, Apple TV, Google TV / Android TV, and desktop browsers. Test video and music playback, notification sounds, in-app audio cues and media controls with the device's real audio, not just the screen.

Question 9

Can I test with VoiceOver or TalkBack on a real device?

Accepted Answer

Yes, on both platforms: VoiceOver on iPhone and iPad, TalkBack on Android. Turn the screen reader on from the panel in a live session and drive it with Previous, Next, Activate, Back, Home and Read All, or with the arrow keys and Enter (plus the rotor on iOS). No gestures to memorise. The panel shows the exact text the screen reader speaks for each element as a running transcript, and the spoken output streams to your computer with the rest of the device audio. Missing labels, a wrong reading order and unhelpful announcements show up in writing, not only in the audio. Switch the device language, or only the app's, to check it in every language your app ships in.

Question 10

Can I run accessibility audits on real devices?

Accepted Answer

Yes. Run an accessibility scan on a real iPhone, iPad or Android device and get an audit report of what it finds — from the console, or let your AI agent run the same scan over MCP and file what it finds in Jira, Azure DevOps or TestRail. Pair it with the screen-reader panel (VoiceOver or TalkBack) to check how the screen actually reads, and with device or app language switching to repeat the check in every language you ship.

Tests d'applications Flutter sur appareils réels

De vrais iPhone et Android pour Flutter

Inspectez n'importe quel écran Flutter

Appium via l'accessibilité

Des agents IA pilotent l'application via MCP

Capture et simulation réseau

Lecteurs d'écran et changement de langue

Étiquetez un widget, trouvez-le depuis Appium

Exécutez votre build Flutter sur un vrai appareil