Hi all,
I’m working with the Automated Test Framework (ATF) in ServiceNow and running tests using the Client Test Runner.
I’ve run into an issue where my functionality relies on native browser dialogs such as alert() and confirm().
The problem is:
- My client-side logic includes a confirm() (or alert()) dialog
- When running the test in ATF (Client Test Runner), the dialog does not appear
- The test cannot continue because it expects user interaction (OK/Cancel)
I was expecting that, since the Client Test Runner is interactive, the dialog would appear and allow manual interaction, but this does not seem to be the case.
Is this expected behaviour in ATF?
If so:
- Is there any way to enable or interact with these dialogs in ATF?
- Is it possible to add an ATF test step that can handle or simulate interaction with alert/confirm dialogs (e.g. clicking OK or Cancel)?
- Or what is the recommended approach when test logic depends on confirm() style user interaction?
Any guidance or best practices would be appreciated.
Thanks!
