A project environment does not necessarily correspond to a separate physical server. Rather, it is a logical environment consisting of a database and a copy of the software packages.

Project environments are therefore the equivalent of test tubes in a laboratory. We check the content, note the changes we make to it, and record the results of the tests we do. As the project progresses, the environments will increasingly resemble what will be found in the production environment.

To set up a large-scale project, the test strategy requires, on average, 10 environments. Here are a few of them.

Project environment #1: The functional sandbox

It is in the functional sandbox that tests are carried out without risking compromising the work in progress in other environments. It allows changes to be made and tested before applying these changes to other environments. Software and business experts are the ones who use this project environment.

#2: Functional tests

To test well, there are several test cycles. We can think, among other things, of the two functional test cycles, the data conversion cycles or even the two integrated test cycles. Two functional test environments are usually active simultaneously throughout the cycles listed. These environments are also used by software and business experts.

#3: Development

In a project, there are two development environments. The former is used to develop data conversion programs. The database for this environment is frequently emptied and reloaded. The second environment is more stable than the first. In it, interfaces, reports, and screens are developed and tested without experiencing the fluctuations of the database in the first environment.

Project environment #4: The technical sandbox

This environment allows technical experts to test software, patches, and patches without risking interfering with the work of other teams. It often happens that the implementation of a patch causes additional problems: this is why the technical sandbox exists. Once a patch has been tested, technical experts can safely install it in other environments.

#5: Training

At the start of the project, this environment is used to train project teams. Afterwards, this environment is used to train users. A separate training environment allows the database to be reloaded before each training cycle. This way of doing things allows trainers to reuse the same examples and users to reuse the same exercises during practical work.

#6: Gold

This environment is used as a reference and contains all the application settings that are included in the scope of the project. In this environment, the configuration management process is initiated. The objective of this stage is to promote and note changes to parameters that come from test environments on a daily basis. The Gold environment is also used to copy it and create the other environments of a project. It is therefore used to create the production environment and allows for a more efficient process during production.

Project environment #7: Certification

The project team manages all project environments except certification and production environments. These are managed by the operational team. The project team therefore hands over all the components of the solution to the operational team. For its part, the operational team installs these components in the certification environment. It also ensures that they function properly before installing them in the production environment.

#8: The production

This is the environment that users will access in order to use the new solution. This environment is not accessible by the project team.

Variations to the environments covered here will be necessary depending on the nature and scope of the project. We must first define the objectives of what we want to implement and specify our needs. Moreover, do you know how to choose the right ERP for your situation ?

You might also like this article: Software testing strategy: a risk management approach.