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.