Test Environment
Four51’s test environment is designed for both client and internal resources to evaluate configurations, products, and templates before deploying them to production.
Details
Four51 provides a test environment that exists separately from the production/live environment. It is an exact replica of the production site in terms of the code base. It can be used to test/demo rebrands, XML, punchout, themes, troubleshoot issues, test uploads, etc.
How to Access:
Additional details on how the test environment differs from the production environment:
- The test database and files are refreshed nightly with data from production. For example, if you create a new product on production today, it will be on test tomorrow.
- Test files include project files, themes, product/category/company images, etc.
- Emails - No emails are sent out on test. So, if you submit an order, no order emails will be sent to you or your customers.
- XML - If you want to test cXML Order Request, let us know which URL you would like XML to be sent to and we can set it up.
- If you create anything on test specifically like a product, then it will get overwritten that night. If you upload files like themes to test, they will get overwritten each night. If you want anything to be permanent, create it on production first.
- Punchout - Testing punchout on test is possible and suggested with doing a punchout implementation. The key thing to keep in mind is you can't have a user punchout to production, but then send the final order to test. When testing punchout, all transactions must be within the same environment (test or production). This is because there are encoded strings that are specific to an environment.
- Batch Upload - If you are testing batch upload on the test environment, you will not receive an email when it is complete, so you will just need to go back after a minute and check to see if it has completed.
Reference Material: none
Related Articles:
Labels: Environment, testing, troubleshoot, sandbox site