Skip to content

Testing Environments

Setting up a testing environment for the modules when upgrading websites can be useful for previewing your changes without interfering with the current website. Not all integrations require a testing environment, so be sure to check the list below to see if you need to use one.

Who Needs a Testing Environment?

YES – If you are creating a new website (or updating an existing one and the client’s current website is already integrated with version 2 web modules), then you would benefit from using a testing environment.

There are two testing environment methods:

  • Option 1 – Query String ParameterThis method uses a querystring parameter in the url, to temporarily apply a template to the CM/MZ-provided pages, without affecting the live site. We recommend this method for small integrations, where very little testing is required. » Read more.
  • Option 2 – Create a Dev Sub-domainThis method uses a completely separate subdomain from the live site, allowing integration of the dev subdomain without affecting the live site. Though there are a few additional steps to set this up, we strongly recommending setting up a dev subdomain for the smoothest experience possible. » Read more.

NO – If however, you or your client meet either of the following criteria you need not worry about setting up a testing environment, as none of the current website’s pages will be affected (all of the module content is hosted on our servers):

  1. You are performing a ‘first-time’ integration (e.g. the client’s website has not previously been integrated with the CM/MZ-provided modules)
  2. You are performing an upgrade from ChamberMaster’s Legacy (JSP) modules to the version 3 modules (if the URL’s on the current site are on the domain and include “.jsp” and “ccid=###” the client is most likely using the Legacy version)

If you do not need to setup a testing environment, feel free to move on to our Quick-Start Guide.

Scroll To Top