QA Wolf

"If you fail to plan, you are planning to fail." - an 18th century inventor who went by the name of Ben Franklin #softwaretesting #softwaredevelopment #qaengineer #developer

iOS crashes cost you users. 71% of users who hit two crashes in their first week never return. With mobile quality a top concern for IT leaders, unstable iOS releases aren’t an option. That’s why, at QA Wolf, we built a fully automated iOS device farm from scratch. Real iPhones. Wired into CI. No flakes, no simulators, no guesswork. I’ll be sharing the full story with Caleb Masters on August 28 at 12 p.m. PT—how we went from garage prototype to production-grade device farm. In the webinar we’ll cover:  📱 Why simulators and existing device farms don’t cut it. 🛠️ How we built our own rack of iPhones. 🔒 What full control unlocks for mobile teams. Sign up today: https://lnkd.in/gDF2SYz2 #mobiletesting #iOS #qa #softwaredevelopment

Meet John G., Principal Testing Advocate in San Francisco, CA. 🚎 John found his way to programming “totally by accident.” While working with data, he started writing scripts to automate tedious tasks, and taught himself how to program. That led him to software testing in 2000, where he discovered both the challenges and rewards of quality assurance. So, naturally, he started blogging about it. Little did he know that one particular blog post, “The cost of automated end-to-end testing,” would lead him right to QA Wolf. We found John when he tagged our cost calculator and blog posts within his own blog. Or rather, he found us. Today, John writes technical blog posts, guides, and ebooks focused on testing infrastructure and strategy. His favorite project so far has been “Mastering the Art of Test Infrastructure,” a deep look into how testing environments work at scale. It gave him a chance to combine his programming background with infrastructure research, and remember why he’s happy writing instead of coding full-time. Whether it’s writing, testing, programming, or conducting a punk rock orchestra—he approaches every project with the same passion and technical precision. We’re glad to have you on the team, John. 🎸

You need better iOS mobile test coverage. Simulators don’t match real device behavior. Popular device farms are slow, expensive, and hard to manage. That’s why we built a physical iOS device farm for our customers. Jaden Lemmon started in a garage with racks of iPhones, tangled USB hubs, and a lot of trial and error. We rewired everything. Expanded the trays. Fine-tuned the processing power of the mini-PCs. Now that same setup runs from a secure, climate-controlled data center. Hundreds of tests. Real hardware. Real coverage. It’s how QA Wolf catches mobile bugs before users ever see them. And it’s ready when you are. Watch how we built it in the comments. #MobileTesting #SoftwareTesting #iOS #Apple

So, you want to start testing your app but have no idea where to start. We got you. #SoftwareTesting #Tech #CTO #QAEngineer

Thirty Madison is saving over $1M per year on QA engineering—without sacrificing safety or speed. 🚀 Thirty Madison, a leader in chronic condition care, needed to replatform two complex systems into one, while maintaining patient safety, development velocity, and patient access across web and mobile. QA Wolf introduced preventative care into their QA process: 🧪 10x increase in test coverage, growing from 200 to 2,000 automated test cases. 💸 Saved $800K–$1.25M/year by offloading the workload of 8-10 QA engineers to QA Wolf. ⏱ Reclaimed 20% of developer time previously spent on manual QA. #Healthcare #SoftwareTesting #SoftwareDevelopment

If your team’s #mobile QA feels like a constant game of catch-up, you’re not alone. The popular “solutions” offer their customers mobile device access, not automated test coverage. Flaky tests, missing coverage, and slow feedback loops? Still your problem. In this on-demand webinar, "Automated Mobile Testing Without Tradeoffs," QA Wolf CEO Jon Perl 🐺 explains why most mobile testing setups fall short—and how QA Wolf built something better. What we cover: 👉 Why today’s most popular device farms can’t deliver reliable E2E coverage. 👉 How we test #iOS on real devices and Android on custom-tuned emulators. 👉 What real QA looks like when tests run in parallel, failures are investigated for you, and results land in 15 minutes. No extra headcount. No infra lift. Just mobile QA that helps your team ship faster. #ProductLeadership #App #MobileTesting

Only you 🫵 can write good bug reports. 🐻 #SoftwareTesting #SoftwareDevelopment #QAEngineer #QA

Running E2E tests on every pull request is usually considered the gold standard, but I’ve found that it tends to slow down teams and creates unnecessary noise. Instead, I recommend “release trains” which is our internal name for shipping and testing release candidates (RCs) several times a day. Here’s why: 💻 You’re actually testing the right version of the app. PR tests are run on individual branches before they’re merged with different combinations of dependencies, settings, or code that won’t reflect the final state of the app. RCs lock in the exact combination of merged changes that are going to production so you're testing what will actually ship to users. 🎧 You reduce the noise. When you avoid triggering flaky tests on every PR, you reduce the background noise of false positives. 🧱 You don’t need to maintain as many build jobs. Testing PRs creates bottlenecks in CI, requiring additional capacity to mitigate; whereas testing RCs means you don’t need to overprovision your release infra. 🔍 It’s easier to pinpoint the source of a bug. With PR testing, the builds and the environments get out of sync, and identifying which PR introduced the regression can be a bit of a guessing game. But because an RC is a specific set of pinned versions, any bugs had to have come from one of them. The main blocker is set up. RC testing takes more effort up front because it treats the release as a single product, not a stream of PRs. That means more planning and prep—but the tests are more reliable so your team ships faster. It may take time to shift your thinking, as PR testing has been known as the fastest way to ship. But in reality, you can ship faster and more reliably by testing RCs. Instead of breaking things for the sake of speed, move fast and keep things intact. So, what do your release cycles look like? Do you think RC testing would change the way you test and release for the better?  👀 #QAEngineer #SoftwareTesting #SoftwareDevelopment

When the usual device farms didn’t deliver the speed, accuracy, or control we needed for #iOS mobile testing, we did what any good engineer does: we built our own. This is the story of QA Wolf's iOS device farm. From a garage in Oklahoma City with fans humming like a jet engine, to a secure, climate-controlled data center. Along the way we wired, rewired, and triple re-wired dozens, then hundreds of iPhones — burning through trays, USB hubs, and more than a few cables. All with the goal of providing the fastest, and most comprehensive automated testing for iOS apps to spot bugs before your customers ever see them. See the hard work it took to make iOS testing easy — full story in the comments. #Mobile #MobileTesting #SoftwareDevelopment