When you manually add steps, first you need to choose a type of step. There are 2 basic types of steps:
- Double click
- Right click
- Hover (mouseover)
- 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
- Set variable
- Answer a prompt - for accepting or declining browser alerts initiated by
When to use it?
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.
When your app has a specific interaction on double-click, for example, double-click to open a file
When your app has a custom context menu on right-click
Important! This action is not recorded automatically. You need to enter "Hover" mode during the recording. 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 handles the scroll automatically.
Press mouse button
This action will initiate the
Release mouse button
Release the mouse button (
When your app has a slider that is interacted with by a drag&drop interaction.
What it does?
Types text into
Chooses a specific option in a native HTML
Removes all characters from a text
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.
Simulates "choose file" action in a form of type
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.
Answer a prompt
Accept or decline browser alerts initiated by
confirm()or provide a custom text answer for a browser
- To confirm the window prompt enter
truein the answer field.
- To reject enter
prompt()questions, enter a custom text that should be provided as an answer