![BlogImage.jpg](https://t4.ftcdn.net/jpg/03/14/92/23/240_F_314922323_au66koEBul4W4k9NlMTvxvSNKHACcMG2.jpg)
Abstract
To define which configurations for testing, you should consider the following:
Development – For Unit, and certain Integration tests.
Testing – For the majority of the tests.
Live – For final performance and stress tests. Also for acceptance tests with the customer.
You will also need to decide which instances you will need where (usually at least one of each for all levels of testing):
Author – This instance allows authors to input, and publish, content.
Publish – This instance presents the website in its published form for access from visitors.
Should be tested in conjunction with the Dispatcher.
Finally, the actual hardware must be considered - any performance tests should be made on a system as close in configuration to the final live environment as possible. For this reason, it is also recommended that the Project Launch be split into a:
Soft Launch – Reduced availability; which allows time for performance tests, tuning and optimization under realistic conditions on the production environment.
Hard Launch – Full availability.
Read Full Blog
Q&A
Please use this thread to ask the related questions.
Kautuk Sahni