How Test Center works

To offer the most effective functionality, Test Center makes requests from a real browser just like an end user would. This lets you test all objects on a page, including those constructed by client-side scripts. In comparative testing all redirects are chased and any infinite redirect loops are detected without the dependency of a manual tester maintaining an updated list of URLs.

There are also three things you should keep in mind when using Test Center:

  • All Test Center requests are allowed. You don't need to allow them manually even if you apply access control lists or header stripping.
  • ‚ÄčAkamai‚Äč originates all test requests within the United States. Sites that use ChinaCDN can be tested as they behave independently of ChinaCDN. The behavior of those sites as they behave on ChinaCDN cannot be tested.
  • When running the comparative testing on the staging environment, Test Center purges the content cached under your CP code. With the content cached, Test Center could run comparisons or verification logic on out-of-date data and it could lead to false positives or negatives. Purges improve the validity of the executed tests. Test Center never purges content from the production environment but the cached content may interfere with the accuracy of the test results.