What is the JAVA development environment, the test environment and the production environment, and its processes __java

Some answers, plus personal understanding, have been collated from the Internet.

The environment is divided into the following categories:

1. Development and configuration of the environment: all development and configuration in this environment. In general, only this environment can be configured and developed, and typically does not create data in this environment . (Development environment is the development environment on each developer's computer, only developers can configure and develop, write data tests in test environments)

2. Test environment: New development and configuration through the system transfer to the test environment, functional testing, you can create data . (developers end up uploading to SVN, testers download and test.) Our testers do not understand the IDE, so they are downloaded by our developers, who are tested directly through IP address access. ）

3. Pre-production environment (not required): from the production environment from time to time, maintain and production environment settings, data consistency, but also for testing, it and the test environment the biggest difference is that it and production system synchronization of the highest, almost the same, some tests, such as the need for large amounts of data, Using this environment test to see program performance is more accurate than using a test environment (in general, less data). (not necessary, our company does not)

4. Production environment: the formal use of the system environment. Under normal circumstances, an environment corresponding to a server, there are some companies to develop, test and other environments put to a server. (Downloaded from SVN via FTP, then deployed on the server eclipse, released, Server is Linux)

Tips: Testing the environment is also useful. When providing services to external systems in development, it is not appropriate to directly use the production environment for the use of the system, and the test environment is of little risk. Therefore, after our product is on line, the test environment still wants to coexist with the production environment, and maintains the open state (the test environment and the production environment are consistent, uses the test environment The goal is, the test, does not affect the on-line item the normal use, and so on test completes, then on production environment. ）

-----------------------------------------------------------------------

General company how to build Java development, testing, production environment

The most used code hosting is SVN, local development with windows+eclipse, production environment with Linux (that is, ftp from SVN to download the project, and then deploy on a Linux server)

From development to submission, test to production environment is how the process. The process is as follows:

1. Development under Windows:
2, submit war to SVN or FTP server, testers download, deploy, build test environment.
3, test Environment: Windows under the Test and Linux under the test, testing functional testing and performance testing, such as LoadRunner or JMeter. The purpose of the test is to check the vacancy and make the product more robust.
4, after the test staff to solve the bug, repackaging, into 2.
5, backup functional code and war, submitted to PM, determined to let testers deploy to the formal environment. and then into 3.
6, write a book, the use of instructions.

There are many tools for managing your code, such as CVS,SVN, or even FTP. There are many things to use in the development process, from the design process to the release run, the tools can be used.

The more formal is:

Development team just development, what to do is to implement the function checkin code to svn/cvs/

The packaged team downloads the latest version of code from the Code hosting server (SVN, etc.), hits the product package, and publishes it to the test group

The Test team deploys the product package and tests