ATF test fails - "Client test runner closed or navigated away while step was running. If this was not intentional, it may have been caused by opening a page with a framebuster. Pages with framebusters are not currently testable"Issue When using Custom UI test step, client running attention is redirected to the service portal completely and test case is getting failed with the below error message."Client test runner closed or navigated away while step was running. If this was not intentional, it may have been caused by opening a page with a framebuster. Pages with framebusters are not currently testable"ReleaseAllCauseFramebusting is not currently supported in ATF. Attempt to reload/redirect from an UI page which framebusts the internal test runner frame. Framebusting prevents functioning when loaded inside a frame, causing failure of test. We usually see this error if there is a custom widget / scripts where there is a redirect involved.ResolutionCheck the custom widget, CSS includes and\or JS include(whether they are using a framebuster) of the customized theme\header\footer of the service portal which was used in the ATF. If found, remove the widget or script from the Service Portal.