Creating a test

Learn how to create your first test and ensure that your users can always get from point A to point B in your application’s flows.

Waldo is designed to test your app from the perspective of the user experience. Our philosophy is simple: if you know how to navigate your applicationapplication - An application (sometimes abbreviated to app) is the primary entity in Waldo. It corresponds to a mobile app on either iOS or Android. Typically, an app in Waldo is distributed on the App Store (iOS) or Google Play (Android), or is intended to be so distributed. (Enterprise distribution is not supported.) An application in Waldo is specific to a single OS platform. Therefore, a mobile app that supports both iOS and Android requires two distinct applications in Waldo. on your phone, then you already know how to record your flowflow - A flow is a sequence of interactions (tap, swipe, etc.) that defines a user journey in an application. A flow can start either at application launch from a pristine state (fresh install) or from the last step of another flow. In the first case, the application is launched in a pristine state from a fresh install. In the second case, the other (preceding) flow is called a dependent flow. on Waldo.

How to record a test:

  • On the Waldo Tests dashboard, locate the + button on the top left of the navigation bar.
  • Hover over the + button in the navigation bar to display the contextual menu and select Create Test.
  • Click the dropdown menu to select the specific buildbuild - A build is a specific instance of an application created at a specific point in time. A build can be an IPA (iOS), a (zipped) “.app” bundle (iOS), or an APK (Android). Ideally, a build should be uniquely identified by version number (and build number on iOS), but Waldo does not require it. to run your tests on.
  • Select one or more dependencies if necessary.
  • Click the Start Recording button to launch the recorder.
  • Once your app is launched on your screen, begin interacting with the application the same way you would on an actual device.

For more on recorder interactions visit Interactions

  • Once you complete the desired flow, name your test using the input box in the top left of the screen, then click the Save test button.

Another modal window will appear to preview each interaction in the test before saving.

  • Click the Save test button to save your test and return to your Tests dashboard.
  • Click the Cancel button to record more interactions for your test.

Note: You must name your test in order to save.

Congratulations! You have just created your first test! From Signing up to Logging out, create tests to establish a core test suite of flows for each new buildbuild - A build is a specific instance of an application created at a specific point in time. A build can be an IPA (iOS), a (zipped) “.app” bundle (iOS), or an APK (Android). Ideally, a build should be uniquely identified by version number (and build number on iOS), but Waldo does not require it. of your application.