"PM" test phase source and test environment version control

Reprint Please specify source:Jiq's technical Blog

For the enterprise information System, personal experience that in the integration testing process need to avoid the test environment is changed, two reasons:
(1) If the modification is wrong, will affect the test, or even interrupt the test;
(2) If the correction is correct, the tester's bug can not be reproduced, the tester's work will be questioned.
And you can't always make sure the changes are correct.

At the same time the source code can not be modified, because can not test the end, found that the source code and test environment of the system is inconsistent!

So we need to control both the source code and the test environment's commit permissions.
(1) The test environment needs to be completely disconnected from the outside world, can not copy things into the test environment it is best to disable the database write permissions on the tester,
Because the test environment database is built by the Deployer with initialization scripts for final product packaging, if the tester modifies the metadata or the data
Dictionaries and the like do not apply as a deployer, then the modifications will not be reflected in the database initialization script that is ultimately used for packaging.

(2) Source code is best to use SVN management (by Project), start testing when you close everyone svn commit permissions.

"PM" test phase source and test environment version control