Which table has Automated Test Framework Step Data? Cloning Down

[Waleed2]

Hi Everyone, 

So we recently implemented Automated Test Framework in our Dev and Test environment. I built out all the tests in Dev and used an Update Set to push it to Test environment, For some reason, the Tests, Steps and the Suites got copied down in the the Update Set and when it was committed in the Test environment, none of the Steps data came with it. For example, when a Field Value Validation was created, the description, name, etc., came except the actual values of the Step. 

As you can see, the Table field is empty and there aren't any conditions listed. Not sure why the Update Set didnt capture it. My question is which table needs to be exported manually to have the steps field filled in when the tests are moved from Dev to Test? 

[Waleed2]

Yes that is correct. All the data that is created is captured in the steps, except the actual fields inside the steps. For example, if you click on a 'Set Field Values' step in your Test instance, does it have the State = Draft, or is it blank? That is the issue I am facing. Whenever I click on the step, none of the actually fields in the steps are pre-filled and I have to fill them up again using the description that got captured in the Update Set. 

[Nitesh Balusu]

As you can see from my screenshots, both instances have state value prepopulated. I didn’t have to go in and add anything and I’ve moved a lot of test cases before without any issues. Please double check once again, try creating something and move it.

[Chris Sanford1 · Accepted solution]

sys_variable_value is the table you are looking for. It should automatically capture in an update set, like Nitesh said. But if you manually import the sys_atf_step XML, it won't copy the values without the corresponding sys_variable_value records. So you need to export sys_variable_value records where table is sys_atf_step.

This link should take you there:

https://<instance-name>.service-now.com/nav_to.do?uri=%2Fsys_variable_value_list.do%3Fsysparm_offset%3D%26sysparm_query%3D%255Edocument%253Dsys_atf_step%26sysparm_list_mode%3Dgrid

[Nitesh Balusu]

I am not so sure if I completely agree to this, because I recently moved all our ATF stuff manually by moving each test step and each test case from our Jakarta instance to one of our temporary london instances and they all worked fine, I manually created an update set and added each step and case to the update set and they all seem to workfine. I never went to sys_variable_value table and moved anything from there.

[Chris Sanford1]

It may depend on the type of ATF step. I did the "impersonate user" step and the actual user was stored in the sys_variable_value table. The way I discovered this, was by doing a show XML on the ATF step record. You can see the "<sys_variable_value>" tags at the bottom of the XML. Also, if you use an update set and look at the payload of the sys_atf_step update that gets captured there is a reference to sys_variable_value in it.