Mobot builds and operates human-supervised, mechanical robots to automate mobile app testing on physical devices.
Mobot uses robots and computer vision to automate physical app testing on over 200 real mobile devices. Supervised by humans, the robots automate business-critical test scenarios, capture results, and integrate reports into your release process.
Mobot is the only solution that uses real, mechanical robots testing on real, physical devices. This means we’re able to successfully cover tests where other platforms fail, and increase your physical device coverage.
Yes - 100% real, physical Android and iOS devices.
No, all robots live and work in Mobot’s New York office.Â
On average, the mechanical robots can accomplish the work in one day that would take humans five days to complete.
Very little. Once you’ve provided us with access to various accounts, builds, and test plans, your dedicated CSM will take over and work with the Mobot team to convert your test plans to automated robot tests.
On average, we can have your tests setup within 24-48 hours.Â
Mobot handles all test plan adjustments needed based on changes to your app.
Most tests can be turned around on the same day, provided we are given notification to start testing before 12 PM EST.
Notify your CSM via preferred communication channels (Slack, email, etc.). Tests can not be initiated by the customer independently.
Our robots use computer vision to compare test results against a baseline to understand whether the test results get passed, failed, or flagged for further review. As part of the onboarding process, we will establish a baseline that the robots use to compare against during testing.
A result may be flagged if the robot reports a bug while testing, and your dedicated CSM is unsure whether your team would classify it as such. For example, if your marketing team changes the color of the login button it may be reported as a bug, but your CSM will flag the result and work with you to understand whether this is something your team cares to see in future reports. If yes, future reports will classify the results as failed. If no, future reports will classify the results as passed.
Yes. You can work with your CSM to select which devices and operating systems you want to use for each test. You may increase or change these device/OS configurations over time as needed.
The Mobot team will convert your test plan into an automated robot test using our internal platform.Â
The most common communication method is a shared Slack channel, but you can choose whatever is most convenient for you.
As the robots execute each test plan, a screenshot and detailed information is captured. This information is reviewed by your CSM, notes are added where needed, and the information is published to the Mobot platform and chosen integrations.
Mobot has over 200 iOS and Android devices available for testing. Speak with your CSM for a full list of the devices and to choose the right device(s) for your tests.
A Mobot team member will intervene, diagnose, and resolve the issue so testing can resume.
An action is a tap or swipe on the physical device.
Apps are installed via standard distribution channels on test devices connecting to customer APIs via secured internal Mobot networks. Reports and artifacts, like app screenshots, are secured end-to-end.Â
Yes, Mobot can handle test plans that include a mobile app and third party device (Apple Watch, Google Fit, etc.).Â
Mobot supports integration via Slack, JIRA, and TestRail. We are always adding more, so if your integration of choice is missing, drop us a line and let's talk.
Yes, Mobot can test in-app payments via credit card.
Yes, we can use different geolocations to execute your test plans.
Yes, Mobot’s testing platform can accommodate biometrics testing (touch ID and facial recognition) using strategic human intervention.
Yes, Mobot can test 2-factor authentication within test plans including SMS, app generated codes, and QR codes.
Mobot can support multi-hour testing cycles.
Yes! Mobot is one of the only solutions that can handle multi-device interactions (messaging, push notifications, etc), as we can place multiple physical devices side by side for the robot to test.
Mobot can handle some performance testing, including battery usage, but is not meant for stress testing.
We do not currently support video recordings of tests.Â
We do not currently support multi-touch testing, but this feature is on our roadmap.Â
Yes, Mobot can support a variety of different accessibility settings that need to be changed on the device, including dark mode, light mode, landscape to portrait orientation, and text size changes.
Yes. You can work with your CSM to select which devices and operating systems you want to use for each test. You may increase or change these device/OS configurations over time as needed.
The Mobot team will convert your test plan into an automated robot test using our internal platform.Â
The most common communication method is a shared Slack channel, but you can choose whatever is most convenient for you.
As the robots execute each test plan, a screenshot and detailed information is captured. This information is reviewed by your CSM, notes are added where needed, and the information is published to the Mobot platform and chosen integrations.
Mobot has over 200 iOS and Android devices available for testing. Speak with your CSM for a full list of the devices and to choose the right device(s) for your tests.
A Mobot team member will intervene, diagnose, and resolve the issue so testing can resume.
An action is a tap or swipe on the physical device.
Apps are installed via standard distribution channels on test devices connecting to customer APIs via secured internal Mobot networks. Reports and artifacts, like app screenshots, are secured end-to-end.Â
Mobot's plans are based on test actions, which are a robot tap, swipe, or drag on the physical device. Contact Sales for more information.
Mobot's standard agreement is annual, but we also offer shorter commitments for those who need flexible terms.
Each plan includes a predefined number of test actions which can be used throughout the month to execute test plans. An action is a tap or swipe on a physical device.
