We’re getting ready to launch a brand new product on Product Hunt very soon, so naturally the team is working tirelessly toward making that day a success. But before we talk more about Playground, let’s hit rewind and talk about …
Waldo Blog Articles.
In 2007, Apple changed the game with the release of its first iPhone. Soon, installing applications on our mobile devices became the norm. Fast forward 10 years and the mobile app industry is thriving. In 2017, there were 178 billion …
Black box testing is kind of a fancy way of saying “have someone use your app and see if it works right.” It’s a method of testing the requirements and functionality of software without the knowledge of its internal structure. …
I’d like to introduce you to waldo’s newest buddy, Walbot. Walbot lives in the great unknown between Slack, AWS, and Github. There, he performs great magic that provides our team with an extra layer of security and more seamless collaboration. …
We walk through the difference between visual testing and functional testing for your mobile app and why you need both for an optimal UI for your customers.
We’re excited to share you can now have your mobile test results sent straight to Slack every time you push a new version of your app. That way, your entire team (or just key stakeholders – that’s up to you!) …
This is part two of a two-part interview. Read part one on developing mobile QA processes for customer reliability. Last week, we shared part one in our interview with Square. We discussed how they create mobile QA processes that ensure …
This is part one of a two-part interview. Read part two here. Mobile QA can be a complex topic, as each product team is testing for something different. That said, learning standards and processes from other app and product creators …
We’re happy to announce you can now easily create Github issues directly from waldo.io. No longer do you need to leave your build version comparisons in waldo to report a change on Github. We made it easy for you. We …
In past articles, we’ve talked about how manual QA takes a lot of resources, and of course, a moderate amount of frustration. We’ve also walked through specific examples of how waldo.io saves mobile developers time and money they used to …