Hi @nadaelkady,
The most straightforward approach is to modify your test to impersonate a pre-existing test user for whom the privacy consent has already been accepted, bypassing the screen entirely. Alternatively, you could investigate ServiceNow's system properties to see if there is a setting that allows you to disable the privacy consent functionality in your non-production environments for the duration of the tests. If neither of those options is feasible, a more technical solution involves adding a server-side script step in your ATF test after user creation. This script would programmatically create the necessary record that indicates the user has provided consent, thus preventing the pop-up from appearing when you impersonate them.
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.
