Update clone down process to include ATF

[Ujjwal019]

I am asked to 'exclude' ATF during a clone down from PROD so that the info isn't overwritten. How I can update our clone down documentation to include this?

#ATF, Automated Test Framework, ATF Clone

[Community Alums · Accepted solution]

As best practice says cloneing geos from production downwards and ATF is adviced never to be used on production instances but test and dev ones, you need to use excluders and preservers in the clone module. Just add the entire ATF structure (plans, tests, suites, etc) to exclude and same as preserver.

[Ujjwal019]

Hi @Community Alums , Thanks for your reply 
So for the basic structure, Should I include all these below tables in the Exclude Table Clone Definition

1. sys_atf_test     (ATF Test)
2. sys_atf_step     (ATF Test Step)
3. sys_atf_test_instance (ATF Test Instances)
4. sys_atf_test_result   (ATF Test Result)
5. sys_atf_step_result     (ATF Test Step Result)
6. sys_atf_test_suite   (ATF Test Suites)
7. sys_atf_test_suite_result   (ATF Test Suites Result)
8. any other custom ATF Related tables that an instance might have (Optional)

I want to preserve all the ATF Data after the clone

To be more specific what tables and data I should include in Exclude and Preserve criteria respectively

Please tell me what are the other measures needs to be taken in ATF while cloning

[Community Alums]

Yes this should suffice.