1. When you think about the quality of your QA strategy, is test coverage your primary metric for success? Does test execution time creep up as your product matures, as more and more test cases are added? Are bugs slipping through the cracks regardless of how many tests you run before release?

    Read more.
  2. More tests doesn’t always mean more coverage — in fact, we’ve found that utilizing a smaller group of tests strategically can be far more impactful than building a huge database. But whether you have 10 tests or 100 tests, a good test database is an organized one.

    Read more.
  3. In the Rainforest Customer Spotlight series, we highlight the superstars of the Rainforest QA platform: the Rainforest project managers (PMs) that write tests, manage databases and help build better quality processes for their organizations.

    Read more.
  4. Our customers want to deploy fast and not be slowed by uncertain delays. One way to tighten their release cycle is by estimating well when a test run completes. However, estimates are hard because each customer has their own tests and environments, and yet being off by minutes or more could add that much to their release cycle.

    Read more.
  5. Good QA requires good communication. Development and QA teams are not only moving faster, but are also more likely than ever to be distributed. In Panaya’s 2017 State of Functional Testing Report, 35% of testing leaders surveyed stated that lack of communication between key users, testers and managers is a significant challenge for their organizations.

    Read more.
  6. Testing is frequently delayed until an application or feature is nearing completion. But siloing QA processes at the end of development just creates lag between the creation and discovery of issues, reducing efficiency. Rethinking where QA lives in your organization and how it fits into the development workflow are the first steps to scaling up mobile testing.

    Read more.
  7. Siloing your QA process, whether that’s with a particular team, in a specific timeframe during development, or overseas with an outsourcing firm, significantly slows down the feedback loop and delays releases. Isolating testing also increases the cost of quality; one study by IBM found that the cost of finding a bug during integration testing is double what it would be if found during implementation.

    Read more.
  8. Kaggle is a platform for data science competitions. I've spent about 3 months of my life competing on Kaggle, and that’s a lot of time! It's about 1% of the working part of my life (in the best case scenario, without any meteorites or nuclear wars). So I need to justify this with some positive, practical perks!

    Read more.
  9. Rainforest Tester Spotlight: Saurav

    Picture of Kristen Hohenstein
    Kristen Hohenstein, October 19 in crowdsourced testing

    Our network of 60,000 crowdsourced QA testers are a critical part of the Rainforest platform, providing the human perspective that allows Rainforest customers to have confidence that their code is bug-free and user-ready. Today we're getting to know Saurav, who has been testing with Rainforest for nearly 3 years.

    Read more.
  10. Whether your team has a dedicated QA manager in-house or takes an “all-hands-on-deck” approach, chances are your testing process has some cross-functional and collaborative moments. We’re rolling out a few new features this month to help Rainforest users collaborate better and get more out of their test writing experience.

    Read more.