How to move application from development server to production server
Hi friends today I am talking about how to move code from development to a production server this is nothing but release management life cycle but it is an important aspect for tester. The Release management discipline covers moving code form a developer’s machine to production.
This will be done in this way:
Developer develops code and runs unit test, integration tests review the code prior to putting it in to the main build, which then leads to Install and build test server, this is where the install team install the code which has come out of the build, if the build does not work then the release manager knows there is a problem, most companies have a code curfew where they make sure developers don’t submit code for the nights build unless they have tested it.
If the install is ok a regression test is run and if this passes, then the code is release to the test team, on one or more ideally two test servers. The testers then run their test scripts against the test plan and test schedule, which is driven by the requirements and change control documents.
Once it is tested by the test team, the code is moved onto the staging server where the business test the code and sign off as to fit for productions, normally referred to as UAT (User Acceptance testing), which is done on a server which is like production, this is where the staging server come into its own, as this is normally the same as production where the normal test servers are normally virtual servers and lower spec. On the staging server the company may also run performance tests which are linked to the acceptance criteria as agreed between the business and the development team.
Then once there is a signature on a release note, down time for productions planned and the release is moved to production and put live.
This will be done in this way:
Developer develops code and runs unit test, integration tests review the code prior to putting it in to the main build, which then leads to Install and build test server, this is where the install team install the code which has come out of the build, if the build does not work then the release manager knows there is a problem, most companies have a code curfew where they make sure developers don’t submit code for the nights build unless they have tested it.
If the install is ok a regression test is run and if this passes, then the code is release to the test team, on one or more ideally two test servers. The testers then run their test scripts against the test plan and test schedule, which is driven by the requirements and change control documents.
Once it is tested by the test team, the code is moved onto the staging server where the business test the code and sign off as to fit for productions, normally referred to as UAT (User Acceptance testing), which is done on a server which is like production, this is where the staging server come into its own, as this is normally the same as production where the normal test servers are normally virtual servers and lower spec. On the staging server the company may also run performance tests which are linked to the acceptance criteria as agreed between the business and the development team.
Then once there is a signature on a release note, down time for productions planned and the release is moved to production and put live.
Comments
Post a Comment