Skip Navigation
Test site (TST) management best practices
Answer ID 11730   |   Last Review Date 12/09/2020

How does Oracle recommend I utilize and manage my test (TST) site?


Oracle B2C Service Test Sites, All versions


A test site (TST) is intended to be a sandbox environment for customization development, staff training, new feature exploration and configuration testing before migrating the work to the production site. Test sites are well suited for agile development. Work is completed on the test site and then moved to production. Element Manager makes moving customizations and configuration very simple between test sites and production. For further information, see Answer ID 11002: Element Manager current capabilities

At least once per quarter the TST site should be refreshed at the end of a development sprint. Refreshing is a "clone down" process where the TST site is destroyed and then a new TST clone of production is created. Refreshing regularly helps keep the TST site on the same version as your production site. A TST site should be a current reflection of your production site. A TST site should not be a code repository or storage location.

Oracle recommends refreshing your test site approximately one week after a production cutover to a new version. TST site refreshes are initiated using Cloud Configuration Assistant. For information on accessing the Configuration Assistant, see Answer ID 7537: Oracle B2C Service Configuration Assistant on Oracle Cloud Portal. For a deeper dive please see our Test Site Details answer.