ATF : should you move to them to production for cloning purposes ?

[Servicenow lear]

Greetings All ! 

We wanted to know if we should move our ATF to production instance for cloning purposes ?

right now whenever we clone prod to non prod instances the some ATF config gets impacted and then we need to roll back. 

Should we move our ATFs to production and disable them and then clone ? 

[Wind0004]

Hi, 

As mentioned in the above responses,  yes it is okay to move ATF's into production if it is causing cloning issues. 

The key check to ensure these don't run in production as that could lead to performance issues. 

The property to check is: sn_atf.runner.enabled

Enable test/test suite execution. The default value is false so that tests don't accidentally run on production systems. Update the value to 'true' on sub-production instances where you wish to run automated tests. This property is private; changes to its value will not move between instances in update sets or team development.

Hope that helps.

Kind Regards,
Wind.

[IbrahimK4837164]

This can actually be a smart solution, especially if you find that your ATF configuration is causing problems when cloning your environment. Moving ATFs to the production instance and disabling them can reduce the likelihood of impacting other environments during cloning. But careful analysis and testing must be done to ensure that ATF will not affect the production environment even if they are disabled.