San Francisco, CA, USA
Jan 24, 2023   |  By AJ Funk
If you’ve got an agile team interested in shipping fast without breaking things, this post is for you. In this piece, I’m going to explain how we at Rainforest QA approach automated testing in a continuous integration / continuous delivery (CI/CD) pipeline, with a focus on end-to-end (e2e) functional testing. The aim of our testing and other DevOps methodologies is to maintain a healthy balance between speed and product quality.
Jan 2, 2023   |  By Maciej Gryka
If you’re new to automated testing for web applications, choosing the right tool can be hard because there are so many to choose from. And if you’re new to test automation, they all sound like they do the same thing—but they don’t. Modern test automation tools mostly fall into three categories: To choose the best automation testing tool for your software team, you need to understand the differences between the three categories of automation tools.
Jan 2, 2023   |  By Mike Sonders
Regression testing—when done well—gives software teams the confidence that their entire application works properly after a code change. But doing regression testing manually is time-consuming, costly, and difficult to scale. As their applications grow in complexity, many teams end up having to throw more and more resources into regression testing—hiring more QA specialists and waiting longer for them to complete testing with each release cycle.
Dec 19, 2022   |  By Mike Sonders
It happens at almost every early-stage startup: a major bug escapes into prod (or into an investor demo). For teams without meaningful quality controls in place, the common reactions are dismay, embarrassment, and the instinct to "hire someone who can own quality." In these cases, “quality” generally means a lack of bugs. While the logic seems sound – there’s a quality issue, so we should hire an expert to handle quality – this instinct is ultimately misguided.
Aug 15, 2022   |  By James Palmer
Manually testing a website can be as simple as opening a web page or application in a staging environment, manually clicking through a list of test cases, and marking whether they passed or failed on a spreadsheet. And in fact, that's where most software teams start when they first invest in QA.
Aug 10, 2022   |  By Mike Sonders
Continuous testing is the practice of testing software as frequently as possible (e.g., multiple times per day) and as early as possible in the development lifecycle. With more frequent updates and faster bug fixes, your product can be more responsive to market changes and the needs of customers.
Aug 9, 2022   |  By Mike Sonders
There are dozens of software testing tools available in 2022 — and they’re not as similar as they may seem on the surface. To choose the right tool for your team, you need to carefully consider the technical skillset of your team and the complexity of the application you’re testing. In this article, we discuss four questions to consider in order to understand the differences between tools.
Jul 15, 2022   |  By Mike Sonders
Automated software testing tools are used to automate interactions with software so tests can be run without a human having to perform each action. This lets one person run multiple tests at once and eliminates most of the human error associated with manual testing. Although there are many types of software testing, functional testing is the most common and the one most teams start with. That’s why we’ll be focusing on functional testing in this article.
Jul 11, 2022   |  By Mike Sonders
In software testing, regression tests are a series of tests run right before releasing a new feature or update to make sure the critical functionalities of your software are still working. Regression testing is done to make sure a new build didn’t introduce bugs into other, existing features of your software.
Jul 7, 2022   |  By Mike Sonders
Smoke testing is the practice of running a small set of tests to ensure the basic functionalities of an application or website are working before moving on to other, more comprehensive types of software testing. For smoke testing to be the most effective, it needs to be completed very quickly so that developers can get fast feedback about the stability of the new build.

Rainforest QA is changing the way QA is done in an era of continuous delivery. Our on-demand QA solution improves the customer experience by enabling development teams to discover significantly more problems before code hits production. Hundreds of companies including Adobe, Oracle and Solarwinds use Rainforest to automate their QA testing process and easily integrate it with their development workflow via a simple API.

No Code Automated Testing:

  • Powering Collaboration: Empower everyone on your team with no-code automation testing. Rainforest Automation rapidly scales coverage and drastically decreases software testing time.
  • Best of both worlds: A new way to write and execute tests combining the best of human and machine based testing. Have both the flexibility of large test coverage and the ability to fall back to human testers when needed.
  • Custom Workflows: Unite automation and manual testing within a single suite and customize your workflow: run against humans for major production releases, run every branch merge against robots.

One platform for both manual and automated software testing.