Report suite configuration for QA and UAT environments in multi-region site scenarios | Community
Skip to main content
Level 2
September 16, 2016
Solved

Report suite configuration for QA and UAT environments in multi-region site scenarios

  • September 16, 2016
  • 1 reply
  • 1037 views

Hi Fellow community members

For the QA and UAT validation approach for a new implementation of a multi-region/locale corporate site scenario, we are exploring two option for testing

1st option - Have a global report suite for QA/UAT environment where data from all regions(close to 25) flows into this single global report suite to check the correctness and consistency of data. When going live to production, we split out individual countries into individual report suites (regular or virtual) and have one global report suite 

2nd option - We have an exact replica of production env architecture in QA/UAT environments also i.e. one global QA/UAT report suite and individual QA/UAT report suites for all regions (close to 25)

Can you please suggest what is the most efficient out of the two approaches above and what is the general practice followed in testing out such corporate web analytics implementations ?

Any inputs would be helpful

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gigazelle

Hi Peeush,

If your localized report suites are going to have identical menu structures, I would recommend using virtual report suites. This means you would only need to send server calls to your global report suite without any secondary server calls. You would only need live + QA/UAT report suites - everything else could be a virtual report suite.

1 reply

Gigazelle
Adobe Employee
GigazelleAdobe EmployeeAccepted solution
Adobe Employee
September 20, 2016

Hi Peeush,

If your localized report suites are going to have identical menu structures, I would recommend using virtual report suites. This means you would only need to send server calls to your global report suite without any secondary server calls. You would only need live + QA/UAT report suites - everything else could be a virtual report suite.