1. The Rainforest team has been working very hard over the past few months to ship a ton of updates to our app. Over the coming months we have some MAJOR performance improvements to the underlying Rainforest platform, but for now let's look at what we've shipped to improve the performance of Rainforest's interface.

    Read more.
  2. All developers will at some time or other have to deploy code that changes the structure of a database. You might have downtime during these deploys due to database changes being required by the new code that you just deployed. There are easy ways to work around those downtimes and provide you a real zero downtime deployment process.

    Read more.
  3. I want to welcome Andy to Rainforest! He's our first Customer Success manager. “Isn’t that just sales?” you ask. Well not really actually. The answer is a bit more elaborate than that. Over to Andy to explain why you should be excited that he has joined the team.

    Read more.
  4. Most web applications are run in more than one place - usually at least two. The first one is the actual server that serves the application to the users. The second is the developer's machine. It's extremely important for developers to be able to test locally before deploying new code to all users.

    Read more.
  5. Version control is something that every shipping team uses, but there's not a lot of talking about the right way to do it. Used properly it can improve your code culture and help you move faster. Let's dive into some best practices for Version Control and the workflow we use here at Rainforest.

    Read more.
  6. Continuous Delivery is a fundamentally new paradigm in software development. In the last 10 years, we've gone from Waterfall to Agile to Continuous Delivery (CD). CD gives you the ability to continuously ship improvements to your customers, with minimal overhead and risk, and is being rapidly adopted across the industry.

    Read more.
  7. We just passed 2 million steps tested by Rainforest, and the number of steps our customers are running is growing exponentially. Our first million steps took us 16 months. The second million took 4 months. We're at 2.5 million steps half way into the third month!

    Read more.
  8. 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.
  9. 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.
  10. 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.