LogoLogo
BugBug HomepageContact SupportLoginSign up free
  • Documentation
  • Tutorial for beginners
  • Best practices
  • BugBug App FAQ
  • Quick Start
    • What is test automation?
    • Start for free
    • Create your first project
    • Install Chrome extension
    • Create and run the tests
  • Creating Tests
    • Your first test
    • Independent tests
    • Duplicating tests
    • New test from here
  • Recording tests steps
    • BugBug overlay
    • Recording clicks
    • Recording hover
    • Recording keyboard typing
    • Recording assertions
    • Recording drag & drop
    • Record from here
    • Re-recording steps
    • Recording pop-up window actions
    • Using keyboard shortcuts
  • Editing tests
    • Grouping steps
    • Components
    • Manually editing steps
    • Actions
    • Assertions
    • Tabs & iframes
    • Variables
    • Local variables
    • Profiles
    • Custom JavaScript actions
  • Running tests
    • Running the tests
    • Statuses
    • Run (locally)
    • Run and pause here
    • Run in cloud
    • Schedules
    • Parallel runs
    • Running via API
    • Test your local build or protected web page using ngrok
  • Preventing failed tests
    • Waiting conditions
    • Smart click
    • Smart scroll
    • Selectors
    • Timeout
    • Delay / Sleep
    • Project settings
  • Debugging Tests
    • Runs history
    • Screenshots
    • Debug in Chrome
    • Breakpoint (run step-by-step)
  • Organizing tests
    • Naming your tests
    • Searching tests
    • Suites
    • Components
    • Projects
  • Workflow Tips
    • Edit & Rewind
    • Changing the test screen size
    • Multiple environments
    • Testing registration & login
    • Integrating with build systems
    • Mobile version testing
  • Collaboration
    • Organizations
    • Inviting team members
    • Alerts
      • Sending email notification
      • Sending webhook
      • Sending Slack message
      • Sending Teams message
  • Integrations
    • CLI
    • Zapier
    • Slack
    • GitHub
    • Bitbucket
    • Gitlab
    • Trello
    • Jira
  • Your account
    • Account settings
    • Edit your name and email
    • Forgot password
    • Manage Subscriptions
    • Account FAQ
  • Troubleshooting
    • Prohibited behaviors
    • Updating Chrome extension
    • Clear cookies and site data for BugBug
    • Testing basic auth password protected websites
    • Common selectors issues
    • CAPTCHA in automation testing
    • Cloud tests sometimes failing
    • IPs list of cloud runners
    • VPN or a Firewall
    • A/B tests
    • Report a bug
  • IN-DEPTH GUIDES
    • Beginners tutorial to automation testing
    • XPath Selectors without coding
    • Tech Leader's Guide to Automation Testing
    • Test automation guides
  • FREE TOOLS
    • BugBug Testing Inbox
    • Example SaaS App
    • No-code XPath Selector Builder
  • Other links
    • BugBug Homepage
    • Pricing
    • Terms & conditions
    • Privacy Policy
Powered by GitBook
On this page
  • Problem statement
  • How does it work?
  • Recording a test with pop-up window handling

Was this helpful?

  1. Recording tests steps

Recording pop-up window actions

PreviousRe-recording stepsNextUsing keyboard shortcuts

Last updated 1 year ago

Was this helpful?

Problem statement

Currently, you can record actions on pop-up windows both during the recording process and while running tests.

This is especially helpful in scenarios where, for example, the user logs in to his or her account using authorization from an external third-party service - e.g. Google authentication or similar.

How does it work?

To put it simply, BugBug forces the opening of a pop-up window in a new browser tab and changes the context for it, e.g. in the scenario of logging in with an external account (e.g. Google auth.), and after correct authorization, the browser tab is automatically closed as if it had happened with a pop-up window.

As an example, we used the Podio page.

Regular view:

While recording the same step/flow in BugBug:

Recording a test with pop-up window handling

  1. Create a new test (or edit an existing one)

  2. Start recording new steps

  3. Record a click action on a button/element that opens a new popup window. Instead of a new pop-up, the page will open in a new browser tab, and the context will automatically switch to that tab as the active tab

  4. Perform all actions on this tab, i.e. provide login details and complete the whole flow. Based on the login flow using an external 3rd party account (e.g. Google account), the tab will be automatically closed when it is completed - just as it would be in a pop-up window, and all actions will be recorded.

  5. When you automatically switch to the currently active tab, you can continue to record actions on that tab

Regular pop-up window
The tab pop-up doesn't appear yet
The pop-up opens in a new browser tab