Handle Website Pop-Ups in Scenario Editor

TheLast userreviewed: willSeptember not21, be2026

knowing

Use this article when exactlyScenario theEditor windowtests mightencounter bebrowser poppeddialogs, upmodal andwindows, haspermission toprompts, handleor application pop-ups.

Recommended guidance

• Identify whether the popup with an if condition so that, ifis a particularbrowser messagedialog, application modal, new tab, or apermission linkprompt.
• Avoid orfixed ansleeps; imagewait is present infor the popup andcondition that matters.
• Do not automatically grant browser permissions unless the usertest recognizescase explicitly requires it.

Validation workflow

1. Trigger the action that particularopens elementthe andpopup hasin toa takecontrolled necessary decisions. Here is an examplestep.
2. Wait for the mentionedspecific situationdialog, andmodal, itstab, implementationor in Appvance Designer.

   Consider user navigatesmessage to www.appvance.com. The user might get a pop up sometimes and sometimes not. Hence we have used an If condition with the Appvance Designer API (_isVisible_Heading("Sign up for email updates")) which returns the Boolean value based on the presence of the heading "Sign up for email updates". If the condition is true, then the further actions are performed onappear.

3. Validate the popup andtext ifor state before interacting with it.
4. Accept, dismiss, or close the conditionpopup isaccording false,to the spantest ofobjective.
5. Return Iffocus condition is skipped for further continuation ofto the script.main

   Hereworkflow isand verify the scriptexpected attachedpage for the above mentioned example

   state.

Popup.dsNote: Older “Designer” wording has been replaced with Scenario Editor terminology.