【Project Management】Different Environments

Development environment - development

Most of them are local environments, and the code can be modified at will, which is convenient for development and self-testing;

Many times, the data used is fake data, because the basic data provided by the database may not have or a certain part of the data. If the system is relatively large, when calling other modules, their data may also be fake data created by themselves. ;

 

test environment - test

A relatively stable environment, try to simulate the online environment as much as possible, generally a branch of the development environment;

At this time, whether it is system configuration or data, it is generally the same as the production environment. It can be regarded as the first batch of users to test the system by its own test team. After passing the test, it can reach the online standard;

 

Production environment - production

That is, the online environment, the environment that users formally use, and the service provided to the outside world;

Restore the data to the initial state, close the error report, clear the original log record, and open the error log record;

 

summary

From development to testing to launch, it is a continuous iterative process;

During development, various logs may be printed, and server resources may be exhausted if you are not careful;
in order to realize your own functions and see the effect, you will create all kinds of fake data by yourself, and then make the database It's a mess;
maybe the configuration is high or the concurrency is too small, and the code you write runs in various ways;

When testing, various data may be missing, but they have to be entered from the page; of
course, there are automated tests, and various test cases must be written;
various user interactions must be simulated, and at the same time In various situations, the various interactions after the situation are not used, and the two layers must be considered carefully;
not only the behavior, but also the number of users must be simulated, and stress testing must be performed in key parts;

When going online, if there is any problem, it takes 3 minutes to locate the problem, and then solve the problem immediately;
no matter what the situation, there must be a corresponding solution;
pay attention to the error log and analyze every exception;
if there is a problem, change the code Be cautious when changing, and can not cause a chain reaction after the modification;

In different environments, I believe that there are different experiences and different focuses.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=325370681&siteId=291194637