Actions
Last updated
Last updated
When you manually add steps, first you need to choose a type of step. There are 2 basic types of steps:
Click
Double click
Right click
Hover (mouseover)
Scroll
Press mouse button (mouseDown)
Release mouse button (mouseUp)
Drag&Drop (BETA)
Type text
Select option
Clear input
Change value
Upload file
Go to URL
New tab
Close tab
Reload page
Set variable
Switch context - for working with iframes or multiple tabs
Answer a prompt - for accepting or declining browser alerts initiated by alert()
, confirm()
or prompt()
.
Action name | When to use it? |
---|---|
Click | 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 test mobile resolutions. |
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 | Important! This action is not recorded automatically. You need to enter "Hover" mode during the recording. Examples when to use it:
|
Scroll | When you need to force BugBug to scroll to specific coordinates. Usually, you don't need to add it manually, because BugBug handles the scroll automatically. |
Press mouse button | This action will initiate the |
Release mouse button | Release the mouse button ( |
Drag&Drop (BETA) | When your app has a slider that is interacted with by a drag&drop interaction. |
Action name | What it does? |
---|---|
Type text | Types text into |
Select option | Chooses a specific option in a native HTML |
Clear input | Removes all characters from a text |
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 |
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