Automated Test Framework (ATF) preserving configuration after Clone

[J_Barratt]

Hello,

We are seeing an issue after we clone where some of the ATF test steps are not being preserved in our Test instance. In the screenshot below I have highlighted the field that is being wiped:

After the clone this field is empty and is required to be filled in on all tests for this to run correctly. In our source instance for the clone, we have preserved all the sys_atf* tables. Any ideas where this field might be stored?

Thanks.

[Henrik Jutterst]

I fully agree with you Chris.

ATF should be handled just like any other changes to the platform. I.E. do your changes in dev/test and then commit them to prod.

AFT should be restricted so that only authorized users can access it. None of these should trigger tests in Prod. When cloning prod to dev/test is done you have your tests and can run them just like it's meant to.

Therefore I see no reason for excluding any ATF-related tables but you might use some data preservers if you have some specific field settings in you ATF-tests.

That's my two cents.
Hope it clears/helps.

Regards

[tracyfischer]

This is the only place I've seen a reference to moving the ATF tests to prod to preserve them, not to run them of course, so is this the recommended method?  It sounds like a good idea to me rather than the overhead of moving them around post clone downs, but it's possible I'm missing something.  

[Marc Clasby]

I did find this KB article:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0722997

This statement is interesting 

It is common, when cloning over a sub-production development instance, that an administrator may want to retain objects associated with the Automated Test Framework. However, ATF tables are not designed to be transferred to the target instance using the Data Preserver, but only through Update Sets.

I am wondering if the ATF "variables" specifically won't work with a data preserver, which is where we run into the same issues posted here. I had added all 21 tables and still run into that one missing component on clone down.

I was going to open a Hi-Support until I found this thread. Are Administrators/Developers promoting ATF tests to production, turning them off and then turning them on in non-prod, bypassing this clone issue?

[Reddy26]

Hi Marc,

By any chance, have you created HI ticket for this issue?

If yes, can you please ping the case number here for our reference.