ATF Test steps broken after import via Update Set

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2018 08:03 AM
On our Dev instance, we created a series of ATF Test Suites and Tests which contained Record Validation steps to validate settings in the sys_properties table. (See attached ATF1.png for an example)
These all worked and returned a 100% success ratio on the Dev instance.
We exported the ATF Suites (including all Tests and Steps) in an Update Set and imported them into our Test instance, where we ran the tests again.
About 5 of 14 the tests returned failures, and on closer inspection we noticed that for every failed test, the 'Record' field on the Test Step form was empty.
i.e. the Test Step was missing an input variable: the name of the system property to validate. (See attached ATF2.png)
All other fields (e.g. 'Value' and criteria, table name etc) were intact.
We've not identified a reason for this yet:
- initial suspicion was that it only affected drop-down fields/related lists, but not all drop-down fields are affected and we have observed this happening to string/text fields
- Update set logs show no errors
- No syslog errors are present on the Dev instance when creating the Update Set
- No syslog errors are present on the Test instance when applying the Update Set.
- Both instances are running Jakarta Patch 5.
Has anyone else experienced this happening? Any ideas for a solution?
(I have searched the Docs site, community, Knowledge base, and Known Errors for ATF in the Hi portal, and haven't found anything).
- Labels:
-
Automated Test Framework

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2018 07:56 AM
This is the issue that I encountered as well. It was NOT a case of missing records because the sys_id's didn't exist on the target system but rather step configs were missing even though the full description was there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2018 06:23 AM
Hi all,
i was facing the same issue that table is empty and User (if impersonate) was empty.
What i did is, i created an update set , went to the sys_atf_step table (1460 records)
Since they were all active , i update them all to Active false (while my update set was turned on)
This took a while and then i updated them all again to Active true.
So i had them all covered in my update set and moved it to TEST.
After that , all fields were populated again and the tests are running just fine.
Hope this helps
Frank
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2018 08:25 AM
Changing atf_step active to false and true again and capturing this in update sets worked for me.
Thanks Frank.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2018 11:15 AM
I'm sharing a solution which Geoffrey Pascua from HI Support shared with me even though my incident was long closed because the issue wasn't consistently reproducible (thanks, Geoffrey!):
... we observed that dictionary entries of “type” Glide Var are missing a serializer attribute.
/sys_dictionary_list.do?sysparm_query=internal_type%3Dglide_var%5EnameSTARTSWITHsys_atf
On out of the box these dictionary entries have attribute serializer defined with value com.glide.vars.VariableValueXMLSerializer.
To correct this, you can do the following:
- Open each record to edit the dictionary records included in the list mentioned above
- Switch to advanced view from related links
- Add to the existing attributes (in the attributes textarea) : serializer=com.glide.vars.VariableValueXMLSerializer

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2019 02:34 PM
This fixed the issue for me. Thanks!