Waldo’s Pipeline Gatekeeper enables mobile teams to integrate continuous end-to-end testing into PRs. Engineers now get test feedback during development to catch and fix bugs earlier and faster.
Hi Product Hunters, Waldo just launched Pipeline Gatekeeper which allows mobile developers to run tests on their PRs to identify and fix bugs before they are merged to the main branch. This enables developers to own part of the testing process to improve product quality and increase product release cycles. Waldo’s product evolution over the last three years has been incredible and this new release is a game changer for mobile development. Take a look for yourself!
@dessaigne@garyfung Waldo takes away the part about having to write scripts. so in essence you can put away appium or detox. and it supports all major frameworks, including swiftui, react native, flutter, etc..
essentially, you have to think of Waldo as the replay engine that allows you to create, maintain and orchestrate your test suite right from the browser
Congrats to the launch! E2E testing for mobile app dev teams on every PR sounds compelling. At PSPDFKit we implemented and maintained this completely ourselves - how much did you have to hook into the xCode and Android buildchains to make it work as a product?
@msch I am not completely sure what you mean by buildchains. For the automation part, we had to piggyback a lot on existing tools by XCode and Android. For the trigger, we basically integrate with all major CI providers, so whenever you generate a build (either ipa or apk) it gets automatically uploaded to us. And lastly, in order to understand the branching structure, we rely heavily on an integration with Github. I am not sure this entirely answers your question.
Hello everyone!
I am Laurent, CTO and co-founder at Waldo. I am so excited that we are announcing the release of Pipeline Gatekeeper today. With Pipeline Gatekeeper, you can now instruct Waldo to run specific tests on PRs. Being able to run Waldo on PRs has numerous benefits, including:
- Faster release cycles because bugs caught earlier in the cycle are fixed faster
- Easy identification of what code changes caused a test failure
- The quality of the builds that go to your QA phase are far higher
- Fewer late cycle delays due to better testing on PRs and main branches
- Confidence that critical flows are tested constantly with test prioritization
We look forward to hearing your feedback!
Thank you @dessaigne for hunting us!
I am Amine, one of the co-founders at Waldo. Since our release of Waldo V2, users and prospects have continued to give us feedback on how we can make Waldo even more powerful to help mobile development teams build better apps, faster. The major theme that we kept on hearing was about bringing a shift-left mentality to mobile developement where the developers are more involved in testing.
I am so excited that we are announcing the release of Pipeline Gatekeeper today. With this new launch, engineering teams can now:
- Run the right test suites at the right times (e.g., on PRs, nightly builds, pre-release, etc)
- Update the tests on your feature branch without impacting the tests run on your main branch
- Share your updated tests across the team once your feature branch is merged
- Merge your test suite in parallel with your code so updated tests can be shared across the team
As you can see, we love feedback so please let us know what you think. I’m also happy to answer any questions people have about Waldo, Pipeline Gatekeeper, shifting mobile testing left, or anything else!
I am so excited to see this product come to life! Shifting mobile testing left to improve the lives of mobile developers, and their users, is going to be a game changer!
Shifting left can have a big impact on engineers ability to merge bug-free branches to master and get a better quality build to the QA team. Amazing progress since V2!
Algolia