1. A few weeks ago, we launched virtual machines for testers. Since then, a commonly requested feature has been to choose a specific browser to try tests with.

    Read more.
  2. This is a guest post by Paul Biggar, Founder of CircleCI.

    Read more.
  3. We recently shipped something I had in mind for a while: running your Rainforest tests against an ad-hoc environment or URL. Maybe you use Fourchette to have one environment per GitHub PR or you have multiple QA environments? You might even use your CI server as a one-off QA environment, as we explain in that post!

    Read more.
  4. If you like many others don't have an optimal environment setup, you are likely lacking an isolated QA environment for your integration tests. Ever wondered why can't you use your CI build server as an ad-hoc QA environment? It's already setup to be able to run your code after all...

    Read more.
  5. We at Rainforest have been using queue_classic for a while now, and we are now the maintainers for it and a few of its extensions too. Our first order of business as new maintainers is making it more awesome!

    Read more.
  6. We've extracted our integrations to a gem so that anyone can add more. If you have a product or service that you think people would like to get hooked up to Rainforest, just go fork our gem, add your integration (check out hipchat.rb and pivotal.rb for examples), and send a pull request our way!

    Read more.
  7. Today we're launching one of our most requested features: to be able to run your tests on a regular but arbitrary schedule. We're calling it the Run Scheduler. It's super useful for running your suite of smoke-tests against Production as a daily sanity check.

    Read more.
  8. Today we're rolling out support for sending notifications to Pivotal Tracker. Once you've enabled this integration, failed tests will show up as bugs in your project's Icebox. You'll be able to see exactly what test failed, as well as a link to a screenshot to help you debug.

    Read more.
  9. As of today, all results from Rainforest include a screenshot, for every step, regardless of if they pass or fail. You don't have to do anything to get this, it's enabled for all.

    Read more.
  10. Today is an incredibly exciting day at Rainforest QA! We've shipped to General Availability a feature that we've been working for the better part of a year: from now on, all of your Rainforest tests will be executed through a freshly created Virtual Machine. So now you get screenshots of what your testers are doing on every step.

    Read more.