1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Amazon’s Mechanical Turk, or MTurk, is a powerful, under-appreciated platform that allows you to allocate work to humans programmatically and at scale. Businesses get access to a vast, scaleable workforce, and workers can select from a variety of tasks whenever they want to work. MTurk can get work done very quickly, with tasks performed in parallel by a multitude of workers. Part of its power lies in the fact that, while it’s programmable, tasks are written in plain English, meaning almost anyone can use it.

    Read more.
  8. Many teams are now “shifting left,” and starting their QA process earlier in the development cycle. But in most cases shift left testing is confined to unit testing alone. While unit testing is a core component of a continuous testing strategy, teams that want to optimize for speed and quality should shift functional testing left as well.

    Read more.
  9. Last summer Rainforest was a 50-person company coming off the heels of raising Series A funding, and the team was overwhelmed. There was too much to do and too few people. As operations manager, I saw an opportunity to build an internship program that centered around creating a holistic learning experience for every participant, while providing much-needed help to our teams.

    Read more.
  10. We've spent the last 6 months working on our biggest platform redesign that will make Rainforest more intuitive and powerful to use, and we can’t wait to share it with you. All the things you love about Rainforest are still there, in a much cleaner and easier to use interface.

    Read more.