Waldo is a continuous mobile app testing platform that helps teams test the final product before shipping updates to the public. It’s the first no-code testing platform that is not based on test scripts, meaning that anyone on your team can easily create and run automated tests. If they know how to use the app on their phone, they can create a test on Waldo!
Waldo supports most native mobile app frameworks, including:
- any native framework: Objective-C, Swift, SwiftUI, Android, Flutter, etc.
- any hybrid framework based on web: Cordova, Ionic, etc.
- React Native
Waldo does not read Open GL.
The first time you create an account on Waldo, it should take you no more than 15 minutes to signup, upload your simulator build, create your first test and run it; and no more than 1 hour to be fully setup with Slack, GitHub and CI integration.
It's a mix of both. Although non-technical people can use Waldo easily, lots of teams whose engineers are heavily involved in the testing process also use Waldo.
There is no scripting involved, ever. Instead, Waldo lets you naturally interact with your app from the user experience. Waldo understands how each screen is structured and the logic that connects them.
Instead of running each test in a suite back to back, we allocate the server resources to run multiple tests at once and return your results faster. Receiving your results is usually a matter of minutes depending on the size of your test suite.
Any test that is deterministic can be automated through Waldo. Waldo was built to give an experience that is as close as possible to the real user experience of your mobile product. Our customers create tests for signups, logins, onboarding, location-based flows, features, divergent user paths, and more.
It depends on what you mean by “changes all the time”. If your app has dynamic content, Waldo can handle that! You will still need to have a stable source of truth that Waldo can use to run each of your new builds.
You can only upload your iOS build as a
.app on Waldo. The IPA format is applicable to physical iOS devices only. While it is possible to generate an iOS build in IPA format that targets simulator devices, it is in no way recommended by Apple, nor does Xcode make it easy to do so. Therefore, you must upload your iOS simulator build as a
.app or Waldo will reject your build.
See Exporting your simulator build for Waldo if you need help to export your iOS simulator build for Waldo.
We currently have a range of devices that covers the various needs of our users, including some of the latest Operating Systems and device sizes.
We support all devices for 4 languages: English, French, Spanish, German.
From Android 9 to Android 11
Pixel 2 - SDK 30.0
Pixel 2 - SDK 29.0
Pixel 2 - SDK 28.0
Pixel 3a - SDK 28.0
Galaxy S10 - SDK 30.0
Galaxy S10 - SDK 29.0
Galaxy A51 - SDK 29.0
Galaxy S8 - SDK 30.0
Galaxy S7 - SDK 29.0
These devices are emulators. By definition, an emulator doesn't simulate the manufacturer layers.
If you’re wondering about a configuration not listed above, contact us!
If you have an SMS verification step in your app’s on-boarding flow, you will need to use a deep link to simulate that step and get to the following screen.
For more information on how to use deep links, visit our step-by-step guide here.
We currently support the following gestures:
- shake phone
- vertical scroll
- horizontal scroll
Waldo was created to help you test the closest build to production and validate that your app works end-to-end. We recommend to only test on one environment to achieve this. Most of our customers choose to test on Staging.
Over-the-air updates are not supported by Waldo. However, most over-the-air frameworks also allow building a static app (that does not auto-update) for every change. if you do that, it’s going to work seamlessly on Waldo.
Short answer is no. Not that Waldo cannot go through these steps when you create a test, it actually can do that pretty easily. But the problem is that these SSO providers have anti-bot systems in place that will make the test non-deterministic and flaky.
Great! We’d love to answer it. Send us an email, or chat with us at the bottom right corner of our website.
Updated 10 months ago