Waldo has received $15 million for its automated testing platform that requires no coding. Waldo allows mobile development teams to put out tests without having to write a single line of scripting code. It then integrates into your continuous integration (CI) process without a hitch.
Today's Series A round is led by Insight Partners, with Matrix Partners and First Round Capital joining in. Nicolas Dessaigne, Ben Porterfield, Tyler Gaffney, and Keenan Rice are among the business angels that have invested. The company plans to use the fresh funds to hire more workers and refine its go-to-market strategy.
The simplest approach to comprehend Waldo is to start by discussing mobile testing. Real-world testing is frequently used by small development teams. They have various smartphone models on hand and use them to test a development build of their software. When something goes wrong, they look for the source of the problem and try to remedy it.
Manual testing does not scale well as your app and team grow. You can create testing scripts, but this is a time-consuming operation that will take longer to complete. Either you have a lot of money and can devote development time to testing scripts, or your developers will eventually forget about them.
Waldo believes there is a third option. The company has spent the last four years developing a testing platform that is simple to set up and maintain. When you first use the product, you upload the app package — the. IPA or.apk file that you get from your development environment — to the platform.
Waldo then launches your program in a browser window. It's a live version of your program that you can interact with the same way that you would in a local emulator. You can, for example, tap buttons, type in a username and password, and swipe your finger over the screen.
Every step of your test is recorded by Waldo. If you use this test in your production environment, Waldo will go through the same steps and notify you if there's a problem — for example, if it can't reach the test's final step. Tests are triggered directly from your continuous integration workflow, which means that when you commit new lines of code to your Git repository, your app is automatically sent to Waldo.
Waldo knows the screen structure, which helps it perform well over time. You can, for example, return to your test and identify screen items. "Imagine you're looking at the HTML in the web inspector on a web page," Amine Bellakrid, co-founder and CEO, explained.
In this manner, you may specify that screen similarity should be more than a specific level, and you can manually customize some elements. You can, for example, select a text box and indicate that it's fine if it's in a different language.
After modifying your test to pass and fail as expected over time, you'll have a true end-to-end testing platform. Waldo not only examines the user interface but also interacts with the app and monitors analytics events. If you perform a Waldo test against your production server, for example, Waldo knows that the server is up and operating because you can log in without any problems.
The company repackages your program and adds some additional code to extract information about it behind the scenes. The company then runs the app on a server simulator. Waldo also uses the emulator to get some information.
Tags : #waldo #nocode #mobile #mobileautomation #15millions