1. Software is still eating the world. As of 2017, there are over 2.2 million apps available in Apple’s App Store that offer a nearly endless array of uses. As software continues to have an expanded role in both business and consumer activities, more and more non-technical companies are developing software.

    Read more.
  2. For many teams, testing processes can’t keep up with development speed. This is especially true for teams that maintain legacy code bases, which are prone to regressions and must be carefully checked before each deployment. Finding a solution that balances reliable results with the speed and scalability that agile teams need to stay competitive can be a challenge. Here’s how PerformanceCentre found a solution to their regression testing roadblock by leveraging crowdtesting.

    Read more.
  3. It’s no surprise that eCommerce sites live and die by their UI. Ensuring that your site or application functions correctly is critical to making sales and keeping customers happy. But eCommerce QA testing can be a time-consuming, labor-intensive process. Many eCommerce teams must maintain hundreds or even thousands of pages and countless visual elements and links.

    Read more.
  4. Shipped: Go-based Rainforest CLI

    Picture of Edward Paulet
    Edward Paulet, April 5 in product

    We’ve made some changes to the Rainforest Command Line Interface (CLI) to make it more accessible to Rainforest users. Here’s what you need to know about the updates to the Rainforest CLI:

    Read more.
  5. Crowdsourced Testing (or “crowdtesting”) can be a scalable, cost-effective way to optimize your testing workflow. The 2016 HPE CapGemini World Quality Report found that 47% of engineering leaders surveyed use crowdsourced testing to as a model for getting fast quality feedback on their product. But for many these teams, managing a crowdsourced workforce is still new and uncharted territory. Implementing crowdtesting can require a shift in thinking and some infrastructural changes that make it a significant investment. So how do you know if, and when, the time is right to try out crowdsourced testing?

    Read more.
  6. QA can be a challenging aspect of development to manage because of its variability. Uncertainty about how much testing to do, time-consuming test execution and the drawn out cycle of finding, fixing and retesting for bugs all contribute to a sometimes lengthy process.

    Read more.
  7. Last night, Rainforest hosted our first [:] futureDev meetup, where we focused on exploring the strategies that teams can use to increase deployment velocity while mitigating risk. Our panel featured experts from Atlassian, HackerOne, GitHub and Rainforest QA to discuss the state of development today, and to share their thoughts on where it’s going next. Here are some of our key takeaways from their discussion.

    Read more.
  8. Building a foundation of critical test cases can be tough. According to the 2016 HPE World Quality Report, 33% of software development teams have trouble knowing what they should test. As a result, teams often test too much -- and waste valuable time running tests that aren’t mission-critical -- or too little -- and miss major issues.

    Read more.
  9. Testing isn’t usually at the top of the list when it comes to agile development priorities. Agile teams are keeping their QA headcount lower than ever before, and many startups are delaying hiring a testing team for as long as possible.

    Read more.
  10. Entrepreneur partnered with CultureIQ to discover the best company cultures in America, and we were thrilled to have been selected among the Top 50 medium-sized companies.

    Read more.