What are Test Environments for?

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.

In this post, we'll examine the importance of having multiple environments and how they can help you isolate your application and prevent accidentally damaging your production systems.

Related articles

Think twice before hiring QA for your startup

Learn why startups usually don’t need to (and often shouldn’t) hire a QA person to improve product quality.

Scaling QA Test Coverage for Consumer Applications

In this post, we’ll dive into how teams can scale QA coverage for consumer apps to keep their testing processes fast and effective.

3 Key Takeaways from QA without a QA Team Webinar

For some organizations (including Rainforest), opting out of building a QA team is an option that’s been growing in popularity. But how do you do QA and keep quality high, if there’s no QA team?

Asking Developers to Do QA Is Broken. Here’s Why We Built a Product to Let Anyone Own QA.

Conventional approaches to QA are broken. Here's a better way.