Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

AEM - Which Test Environments will be needed? | AEM Community Blog Seeding

Avatar

Administrator

BlogImage.jpg

AEM - Which Test Environments will be needed? by Adobe Docs

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

AEM - Which Test Environments will be needed?

Q&A

Please use this thread to ask the related questions.



Kautuk Sahni
1 Reply

Avatar

Adobe Champion

A bit surprised a Stage environment is not mentioned as an option between Test and Prod (unless you go with Soft-launch approach as mentioned in the article, however you then need to handle existing web properties in a multi-tier setup).