Skip over navigation
OroCommerce Blog

Software Development Lifecycle (SDLC) involves multiple activities, such as planning, analysis, design and development, different types of testing, deployment, and maintenance. These activities usually happen in different software environments, which could be classified as development, testing, staging, and production environments. Confusion sometimes arises when differentiating between testing and staging environments. Both are used for testing but at different times during the project. This article aims to clarify the testing vs staging environment puzzlement for business people and those who are new to the subject.

Testing and staging environments


Even though development and testing typically happen simultaneously, you will eventually need to freeze your work and deliver the results to the customer or roll out your new version of the application. This process is called deployment and it usually happens in frequent intervals so that your delivered product becomes MVP-grade (minimum viable product) as soon as possible.

Now, before you can deploy your code from your development environment into the customer’s production environment, there are a few more things for you to do. The first one is testing. To ensure the testing is properly set up, there’s a need for a separate testing environment. It is specifically configured to allow QA specialists to effectively execute their tests and check the system components in different use case scenarios.

The second activity you usually need to do before placing your code to production is the user-acceptance testing. This is when you check the entire system in the exact way it is going to be used in production, including live data volumes and types of data as well as user behavior. This type of testing requires a staging environment, which is identical to your production environment except that it’s not publicly accessible to end users.

Let’s consider the main differences between these environments and why you may need them all during eCommerce implementation.

Development Environment vs Testing Environment

A development environment is configured to enable developers to write code quickly, verify it by creating basic tests (unit tests), and be productive. This environment is much smaller than what it takes to run an entire application in real-life implementation. It also features developer-specific tools that may at times hinder rigorous QA validation. And most importantly, the development environment is constantly changing – with new functionality being added all the time – which makes it difficult for QA engineers to run time-consuming tests, e.g. regression or integration tests, without disrupting the development process.

A testing environment is where QA engineers can use a variety of testing tools to run all their different tests over the application code taken from the development environment. While developers check their code for simple bugs before passing it for quality assurance, QA engineers execute more complex and time-consuming types of tests to check the compatibility of the new and old code, the correct integration of different modules, the system’s performance, etc. Running such tests on the development environment would lead to a huge waste of the developers’ time.

Testing Environment vs Staging Environment

Even though testing is typically performed alongside development, the need for user-acceptance testing on a staging environment is of paramount importance. A staging environment is an identical replica of the customer’s production environment, which also typically contains real production data that’s been sanitized for safety purposes. It is hosted in the same way as the production servers and involves an identical setup and update operations. Therefore, testing on a staging environment offers the most reliable way to check code quality and ensure the production servers are successful.

A testing environment – even though critical for ongoing code quality assurance – can hardly achieve the same real-life degree of the customer’s system emulation. That’s why it is a common best practice to have the application code fully tested on the staging environment before moving it to production. It is considered a must for enterprise applications.

Testing and Staging Environments in OroCommerce

Not all OroCommerce Enterprise Edition licenses come with a staging and testing environment so be sure to ask your Oro Representative if this is a requirement. However, customers can always add development and testing environments to their OroCloud environment for an additional cost. The OroCommerce staging and testing environments feature advanced monitoring, backups, redundancy, and other DevOps capabilities necessary to ensure rigorous UAT testing for a custom-tailored OroCommerce implementation.

To learn more about our delivery model or licensing plans, please contact us and we’ll get back to you shortly. You can also sign up for free access to OroCommerce demo.

Back to top

You will be redirected to [title]. Would you like to continue?

Yes No