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
  • Action types available for a step
  • Mouse events
  • Input actions
  • Window actions
  • Advanced actions
  • Actions - detailed descriptions & tips
  • Mouse actions - details
  • Input actions - details
  • Advanced actions - details

Was this helpful?

  1. Editing tests

Actions

PreviousManually editing stepsNextAssertions

Last updated 16 days ago

Was this helpful?

When you manually add steps, first you need to choose a type of step. There are 2 basic types of steps:

  • Actions

  • Assertions

Action types available for a step

Mouse events

  • Click

  • Double click

  • Right click

  • Hover (mouseover)

  • Scroll

  • Press mouse button (mouseDown)

  • Release mouse button (mouseUp)

  • Drag&Drop (BETA)

Input actions

  • Type text

  • Select option

  • Clear input

  • Change value

  • Upload file

Window actions

  • Go to URL

  • New tab

  • Close tab

  • Reload page

Advanced actions

  • Set variable

  • Switch context - for working with iframes or multiple tabs

  • Run custom JavaScript

  • Answer a prompt - for accepting or declining browser alerts initiated by alert(), confirm()or prompt().

Actions - detailed descriptions & tips

Mouse actions - details

Action name
When to use it?

Click

Double click

When your app has a specific interaction on double-click, for example, double-click to open a file

Right click

When your app has a custom context menu on right-click

Hover

  • Navigation bar with menus that appear on mouseover

  • Cart preview that appears on hover

  • Actions that only appear when you move your mouse over a table row

Scroll

Press mouse button

This action will initiate the mouseDown event. You can use it in combination with "hover" and "Release mouse button" to simulate drag & drop from one element to another element.

Release mouse button

Release the mouse button (mouseUp) on a specific element.

Drag&Drop (BETA)

When your app has a slider that is interacted with by a drag&drop interaction.

Input actions - details

Action name
What it does?

Type text

Types text into input, textarea or contenteditable fields. Simulates keyboard presses, entering characters one by one.

To escape text like {{ }}, you must put it between {% raw %} and {% endraw %} blocks. Example: This is not a {% raw %}{{not_a_variable}}{% endraw %}

Select option

Chooses a specific option in a native HTML select dropdown (also called "combobox" menu).

Clear input

Removes all characters from a text input field, textarea or contenteditable

Change value

Sets a value of any form element. HTML has many form controls and some of them can be set to a specific value, for example, radio groups. Technically a JS "change" event is triggered and the value is updated immediately, without typing letter by letter. Use it for typing longer texts.

Upload file

Simulates "choose file" action in a form of type file for uploading in forms. You can customize the file that's going to be uploaded.

Advanced actions - details

Set variable

This action can be used to store local variables from tested sources. You can use a selector to find a text value on the tested web application. Now you can store any text value from the tested web page in a variable and use it in feature steps. For example, to find out newly registered unique users in your CRM. This variable is also cross-domain.

For more detailed information check out "Variables during recording".

Answer a prompt

Accept or decline browser alerts initiated by alert(), confirm()or provide a custom text answer for a browser prompt().

This action is automatically recorded and most of the time you don't need to edit it manually.

  • To confirm the window prompt enter true in the answer field.

  • To reject enter false.

  • For prompt() questions, enter a custom text that should be provided as an answer

When you want to click a specific element. This is the most common action for navigating the web. This also serves as "tap" action if you .

Important! This action is not recorded automatically. You need to . Examples when to use it:

When you need to force BugBug to scroll to specific coordinates. Usually, you don't need to add it manually, because BugBug .

test mobile resolutions
enter "Hover" mode during the recording
handles the scroll automatically