Difference between Test Server, Staging Server and Production Server

production server
Staging Server
Test Server
In relevance to load testing on an application – what is the difference between test server, production server and staging server?

Answer Wiki

Thanks. We'll let you know when a new response is added.

I would say that load testing should be done in the test environment, as in my opinion, the staging environment is just a final step before putting changes into production, in which you can even give access to users, so they can review content and new functionalities.


Discuss This Question: 6  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Northernoz
    The Release management discipline covers moving code form a developers machine to live/production. This is done in the following order or there about: Developer develops code and runs unit test, integration tests and re-factors 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 hey have tested it. Then the Build is automatically run every night using the code cut form the curfew time. 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 refereed to as UAT (User Acceptance testing), then there is OAT (Operational 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/company. Then once there is a signature on a release note, down time for production is planned and the release is moved to production and put live, make sure there is a roll back position, if not you could end up with production down for hours and a not very happy business. years ago in a roll for a telco, down time of the network was counted in millions per second, even a single cell or part of the min network could lose a Million every 15 minutes, so the pressure was on to make sure the code was tested and a signature was given before moving to the next stage of the release process.
    195 pointsBadges:
  • jaideep
    Thanks Northernoz, it is very well explained.
    30 pointsBadges:
  • PallaviVarne
    Thanks.. It's very helpful
    10 pointsBadges:
  • KatyDorjee
    Excellent note on life cycle of a "software development."
    10 pointsBadges:
  • puttyaya
    It an amazing SDLC!....it is really awesome man....thanks
    10 pointsBadges:
  • awhigham

    Excellent.  I really appreciate this explanation

    10 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: