1. We now return a screenshot for every single test in every single browser. I'm so excited to ship this update because, in the few weeks we've been testing it on our internal skunkwerks version of Rainforest, the product has become way more useful.

    Read more.
  2. Various teams have different definitions of when a feature is done. Is something done when it's deployed? Or when it's merged? Or is it done when it's being used actively by users? The definition will vary greatly depending on your product.

    Read more.
  3. About 6 months ago we set out to simplify Rainforest's web UI, by integrating results and tests in one view, the 'dashboard'. Since the good people that use Rainforest have a broad range of technical ability and familiarity with using developer tools, great usability and simplicity are extremely important to us. Read on for the reason behind this change.

    Read more.
  4. We all use Gmail at Rainforest. Tons of people use it, so we've decided to make it easier for you to get to your detailed results in our app. You may have noticed recent emails from us have extra buttons on them - these are 'Gmail actions'.

    Read more.
  5. At Rainforest, we spend a considerable amount of time thinking about what the ultimate testing workflow is. Let me start by saying that the current state of affairs is much better than it ever was. Developers, for the most part, now understand that automated testing is important. There's good literature written around building an efficient QA process as well as how to do this while still shipping often and fast. Tools - especially for web developers - are better than ever.

    Read more.
  6. Any serious project nowadays needs background processing, right? Most of the Ruby community uses Sidekiq or Resque but there are other options. One is QueueClassic. QueueClassic uses PostgreSQL instead of Redis for Sidekiq.

    Read more.
  7. We've finally shipped our most-requested feature. This update gives you individual accounts for everyone on your team. This is the first in a set of features focused around our enterprise users on our roadmap for the next two months.

    Read more.
  8. Rainforest is the simplest way of doing integration testing. Since integration tests play such a big role in assuring the quality of your software, it is important to run these tests on a regular basis.

    Read more.
  9. Quality Assurance has traditionally been handled by teams of in-house testers who do exhaustive manual and automated testing. This worked great when you deployed every 6 months - but now modern companies like Amazon, Facebook and Google ship hundreds of times every day. It's almost impossible to ship fast and frequently while maintaining quality with in-house QA, and this is hurting your business.

    Read more.
  10. We're very excited to announce the newest member of the Rainforest team, Jean-Philippe Boily (JP to friends and English speakers)! JP is a brilliant Ruby developer who has a great love for Open Source and a dodgy sense of humor, both of which are requirements for fitting in at Rainforest.

    Read more.