BugBug AI test recorder
Border around element pointed by mouse coursor
To record mouseover steps you have to use Add hover
Add assert option on the recorder
"Add multiple" toggle disabled
"Add multiple" toggle enabled
Click "Record from here" to execute test to a given position and enable recording mode
Recording mode in the webapp UI
Recording mode is activated in the browser window with a test
Newly recorded steps with the NEW badge
Movable recoding position
You can pause recording and enable it again by clicking Record button
Change playback position and click Resume button to execute newly recorded steps
You can resume execution from BugBug overlay
Regular pop-up window
The tab pop-up doesn't appear yet
The pop-up opens in a new browser tab
This will bring up the "Pause recording" view with its associated options.
While you are in this view, you can alternatively use two other shortcuts:
\* Ctrl + Alt + 1 to resume recording
\* Ctrl + Alt + 2 that will finish and close your recording session.
BugBug Runner
Components page
Components list
Insert a component to a new test
List of existing components when adding to a new test
Inserting component
Inserting component multiple times in a single test
Parametrizing components with overrided variables
Unlink a component from a test
Removing a component from a test
Component's details page
List of connected tests
Edit mode of a component used in a test
Show related tests
Show related tests
List of related tests with a component
No related tests with a component
Deleting a component without any connected test
Deleting a component with multiple connected tests
Delete in bulk
Click parameters
List of available assertions
Example of assertion modification after recording
Values can be confirmed under certain conditions
Tab numbers starting from 0
Default tab context - Top
Switch to the iframe identified by XPath //IFRAME[id="frame1"] in the first browser tab (tab 0)
Switch test execution context to nested iframe
Mixed test contexts
Example: variable "hostname" used in an URL
Example: definition of variable "hostname" in the variables tab
Variable settings
List of added custom variables
Variables used in a test
Example: a variable used in "Go to url" action
Use variables in selectors, assertions, etc.
| Built-in variable name | Type | Description | Usage example |
|---|---|---|---|
testRunId | Text | The current id of the running test (UUID format). | You want to have a new random unique value for one specific test run, for example you want to test user sign-up and then log in. |
testId | Text | The current id of the test (UUID format). | You want to test add/edit/remove operations in one test, for example, add a product and then remove the same product with a name Test Product {{testId}} |
suiteRunId | Text | The current id of the suite (if the test is running from a suite, UUID format). | You want to have a new, random unique value that is the same across all the test runs in one suite. |
runMode | Text | The current run mode for the test ("local" or "server"). | You want to have different input or assertion value when the test is run on server. |
| randomNameFixed | Text | Random name that remains unchanged during the test run (8 letters). | You want to have a new, random uniqe name that is the same across all the test and used multiple time |
scheduleId | Text | The current id of the schedule (if the test has been started via a schedule, UUID format). | You want to have a new, random unique value that is the same across all schedule run. |
timestamp | Text | The current Unix Time in milliseconds (int format, e.g.: 1645710937798). | You want to know when your test runs or use it similar to randomNumber |
randomNumberFixed | Text | Random number that remains unchanged during the test run (10 digits). | If you want to edit an element, find it later in test steps and use it or remove it. |
profileName | Text | The current profile name for the test. Default: "Default". | If you want to enter a production/test URL depending on the profile, test runs |
suiteName | Text | The current suite name for the test (if the test is running from a suite). | If you want to create an email that inform you about suit name that was run |
testName | Text | The current test name. | You can mix it with timestamp to create a new subscription notification test. |
Two option for variables action in overlay
The BugBug confirmation email is used only as an example of the process.
The BugBug confirmation email is used only as an example of the process.
Add any variable as alias
Combined URL
To add, remove and edit profiles go to the "Variables" tab
Override variables in the profile settings. Leave an empty field to keep the default value.
Variables button in recorder
Click on a "Save variable for later" button
Click the item with the desired text value
No spaces or other special characters allowed
Find an input you want to fill with the variable
Variables added by default to insert list.
Recorded step for local variable
Run and pause here in the webapp UI
Test execution window with option to resume running or run step-by-step
Empty screen for Schedules
Add new schedule modal
Filled form for with a new schedule
Enabled schedule with all tests running every hour
Email notification for a failed schedule
Test suites selected for the daily schedule
List of all created schedules
| Number of parallel test runs | - | 2 | 4 | 8 | 16 | 32 |
|---|---|---|---|---|---|---|
| Billed monthly | $219 | $299 | $459 | $779 | $1,419 | $2,699 |
| Billed yearly | $189 | $257 | $393 | $665 | $1,209 | $2,297 |
| Number of parallel test runs | - | 2 | 4 | 8 | 16 | 32 |
|---|---|---|---|---|---|---|
| Billed monthly | $659 | $739 | $899 | $1,219 | $1,859 | $3,139 |
| Billed yearly | $559 | $627 | $763 | $1,035 | $1,579 | $2,667 |
$ ./ngrok config add-authtoken {{yourAuthToken}}
You can check out it in the browser.
Create a variable
Use it in test
Adaptive Locator generated automatically by BugBug's AI during recording
Selector customization
Nested selectors with BugBug.
The right box is the parent selector, the pink box is the child selector.
Nested selectors options.
To enable step-by-step execution, click on the "Run and stop here" action.
Paused mode. To execute next step click on the "Run next step and pause" icon
Paused mode in a window with a test. BugBug's overlay has options to control the execution process
Example suite run history with auto-retry enabled. There were 3 attempts to run the same test.
Example suite run history with auto-retry disabled. There was just one attempt to run the test.
You after using Edit & Rewind functionality. Source https://www.reddit.com/r/wholesomememes/comments/evgnfp/resting_is_important_to_your_wellbeing/
You can select screen size optiom from dropdown menu
open meatball menu and choose Test settings
choose an option from Screen size dropdown menu
Go to the side menu and select Project Settings. Then select the Screen Sizes tab.
Open meatball menu, choose test setting and use link from Sreen size dropdown menu
Icon will only be added if you set two different screen sizes for each test.
Duplicate the project and change its name
You can choose a mobile option when creating a new test
or change to mobile screen size in test settings.
When You copy an existing test
Run tests with smaller mobilewindow width
Access & Edit all projects
Manage Billing
Update credit card information
Change subscriptions
Blank screen without alerts
Blank screen without alerts
Alerts setup modal
List of available conditions
Send to setup options for email notifications
Method and Webohook URL fields on the setup screen
Verify alert configuration
Request body with a bult-in variable
The API token for the project
Run in CLI option in the more drop-down menu
Run this suite via CLI modal