Waldo now allows you to remove a parent test and replace it with a new parent, without having to re-record subsequent dependent tests. Quickly remove and replace dependencies with an intuitive drag-and-drop interface, and get back to testing!
This should significantly reduce the amount of maintenance required when parent tests need to be updated throughout your suite.
Check out the video below to see the feature in action and read more about this in the Help Center:
Located in the left sidebar navigation just above your user icon you will see a section of the menu devoted to the particular app page you are on in Waldo. Clicking here will take you to a streamlined menu to adjust specific default settings for the app.
You can now:
If you have multiple apps in Waldo, you can toggle between them to adjust these settings on an app-by-app basis.
We are excited to announce that Waldo users can now duplicate tests! This latest update allows users to easily duplicate an existing test: saving time and effort when setting up new test cases.
This new feature will greatly streamline the testing process, and we can't wait for you to try it out. Read more about the Duplicate Test feature here
Previously, the number of devices available in your Waldo account for testing was controlled by our Administrators and dictated by your Waldo Contract. Waldo Administrators had to go in and add additional device configurations to your account if you needed them updated, and we realized that wasn’t helping you test any faster.
Starting today, customers will be able to have access to all device configurations supported by Waldo in their account to select for test runs! Our device selector will show you all available OS for the device type you choose to make setup simple and error free.
Want to learn more about optimizing your device coverage without increasing your maintenance lift or test run duration? Check out this Help Article.
Now, you can easily view all variables used in a testing flow and make any necessary changes. Our new Variable Viewer shows each variable's status and allows you to make changes directly.
To access the Viewer: go to your Tests page, click on the test you would like to view, and use the tab at the top left of the screen (next to Overview) to select “Variables.”
From here, you can see which step the variable is used in (if it is active), the pattern the variable follows if it is inherited, and make any required edits.
Additionally: making a change to the variable at the parent test level will automatically update all instances independent tests with the same change. This should significantly simplify variable management for all current customers!
We've made changes to how we compute the similarity scores for a pair of screens.
Specifically, we now only take into account characteristics that are visible to the human eye (e.g. text, size, shape, position) whereas before we would also rely on some invisible attributes (such as accessibilityIds).
This means that the scores are now going to reflect the reality as seen by an end user, and not the underlying implementation details. Specifically:
You might now see some screens having a different score, and potentially not passing the similarity assertion. If that's the case, you should simply accept the new result state as the reference going forward.
As usual, let us know if you have any questions!
We are excited to announce the launch of Waldo Academy: a series of courses paired with real product use cases, designed to give you an in-depth understanding of Waldo.
Unlock even more value from your testing suite by diving into our best practice tips and testing methodology!
Start exploring by clicking here.
We made several changes to the step modal overview.
As usual, we'd love to hear your feedback on this release!
When you trigger a test run via Waldo API, you can now target a specific version of your application you wish to test by providing the corresponding git commit.
You will find more information in the docs 👉
We've updated branch displays in Waldo to support various git branch statuses! It's much easier now to visually differentiate between default, open, merged, and closed branches to quickly understand whether or not tests updates will be applied globally.
Learn more about how Waldo tracks branches in the docs 👉
