ATF Tests Missing After Clone Despite Table Preservation

[MeenaS678308014]

Hi Community,

We performed a Prod-to-Dev clone in ServiceNow, and our custom ATF tests are now missing from Dev, even though ATF-related tables were configured for preservation. Only OOTB/admin-created tests are visible, and the ATF plugin is up to date.
Note: ATF 's are not available in Prod instance as its available till Pre-Prod.

Tables configured for preservation:

sys_atf_test, sys_atf_steps

sys_atf_test_suite,

sys_atf_suite_test

sys_atf_test_parameter

sys_atf_variable

sys_atf_test_result

sys_atf_test_suite_result

sys_atf_step_config

sys_atf_parameter_set

sys_atf_test_result_item

sys_atf_test_result_step.

Questions:

Are any additional ATF tables required for preservation?

Is Data Preservation the correct approach, or should we use Update Sets?

How can we verify that preservation was applied successfully?

Please suggest the recommended approach to retain custom ATF tests after future clones.

Thank you!

[Ankur Bawiskar]

@MeenaS678308014 

you should push ATF tests to UAT and PROD so that when PROD is cloned to DEV the tests appear in DEV

see below

Clone Tips and Tricks 

Automated Test Framework design considerations 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[its_SumitNow]

Hi @MeenaS678308014 

if you've Configured for Preservation for the above tables , but still your records are not visible, then I'd suggest to log a HI- case on Now Support, because the actual expected behavior is that it should be preserved

If my reply helped ,then please mark helpful & Accept as Solution 🙂

Regards

Sumit

Technical Consultant

[Hemanth M]

Hi @MeenaS678308014 ,

The best approach is to move ATF test cases to Prod and make sure the property sn_atf.runner.enabled is disabled in Prod so that ATF will not run even accidentally.
During a clone, it will come down to sub prod without any issues.