Ability to get the last suite run ID based on suite ID in the public API

There is no option to retrieve the last suite run ID based on the suite ID using the public Bugbug API. This functionality is available in the internal API but is not exposed in the public version. The feature is needed to automate the process of monitoring the status of suite runs.

Bartosz Wachowski 12 days ago

Description for custom variables

It would be useful to have a summary/description for variables. A mock-up :

Marius COJOCARIU 14 days ago

Improving Slack integration

Possibility to send BugBug’s Slack notification on private group.

Bartosz Wachowski 14 days ago

Add shortcut for running one step at a time

With the new recording functionality, there’s an option to run one step at a time using this button: It would be nice to have a keyboard shortcut available for it as well. :) Current setup seems to be: Ctrl+Alt+1 = Resume running Ctrl+Alt+2 = Record from here Ctrl+Alt+3 = Edit and rewind Ctrl+Alt+4 = Finish and close Maybe the sequence could be updated to: Ctrl+Alt+1 = Resume running Ctrl+Alt+2 = Run only next step Ctrl+Alt+3 = Record from here Ctrl+Alt+4 = Edit and rewind Ctrl+Alt+5 = Finish and close

Marius COJOCARIU 20 days ago

Uploading multiple files

There is no option available to upload multiple files in a single action during test creation. It is currently not possible to select more than one file at a time.

Bartosz Wachowski About 1 month ago

Possibility to include more details of suite runs in webhooks

Currently, including details in webhooks is limited to the built-in variables only. It would be beneficial to also include details obtained from email alerts, such as: failed tests count passed tests count test retries count duration started at finished at timezone run by

Bartosz Wachowski About 1 month ago

Compare test runs for easier debugging

Often, when a test fails to diagnose/debug, we need to open the previous execution and see what changed. To make debugging easier, it should be possible to automatically compare test runs.

Paweł Bylina About 1 month ago

Marking feature

Marking feature that allows users to mark test steps that require further work or review without setting a breakpoint. This will help users easily identify steps needing attention without interrupting the test flow.

Michał Rygoł 2 months ago

Correction mode

Correction mode for test editing, which allows users to make multiple changes to steps or texts and save all modifications at the end of the session, rather than after every individual change.

Michał Rygoł 2 months ago

Accessibility improvement at the search functionality in "Suites"

Is there a way to improve the functionality of search results? Right now, I have many tests, and when I try to search for something it’s not clear where my result is. Sometimes I have to scroll a lot before finding the result I want, and even then, sometimes I miss some results. Is there a way for the search to work as in the “Tests” tab? Or maybe improve the highlight, not being only the border of the card?

Wilker Augusto 2 months ago

The ability to stop the running test suite through the API or CLI.

The ability to stop the running test suite through the API or CLI.

Michał Rygoł 2 months ago

2

Aug 6

Make more of the test title visible

Hello. One of the features I feel is missing is the ability to always see the complete test title that I type. Right now If the title is too long I have to click on the field and use either my mouse or keyboard to see the end of the title. Suggestion / comments It would be nice if I could see the entire or simply more text added in the field. Maybe that field could expand when clicked.

Wilker Augusto 2 months ago

Optionally stop following tests in suite when a test fails

We sometimes build suites to run tests in a predefined sequence. It looks like in BugBug there's no way to stop it from continuing after a failure. Test1 OK Test2 fails Test3 (which builds on Test2) continues.. this will always fail and is a waste of time and cpu I rather the suite stopped (in this case) thanks for considation

informa-jojo 3 months ago

Add a label in the project that has power into the schedule runner

Label like "draft", "in progress", "active", "quarantined" or something like these. And if it's quarantined then it won't run or count as failure. The reason for this labels is to easily categorize the script if they are being worked on, testing or has a bug.

Rav Banaag 3 months ago

Add ability to merge two group together

Sometimes I create multiple groups that need to be merged into a single group. But there is no ability to merge those groups into a single one.

Md Zarin 3 months ago

2

Add ability to create GitHub issues

Our company uses GitHub to list issue tickets. It would be great if we could have the option to create GitHub issues directly from the test result. For example: The failed tests will have an option to generate a GitHub ticket.

Md Zarin 3 months ago

User action tracking

Ability to identify which user did what within the test to simplify cooperation and clarification of potential issues.

Michał Rygoł 4 months ago

1

Unlink component confirmation prompt or locking mechanism

Since users report misclicks that lead to unlinking components, it would be good to implement a confirmation prompt or locking mechanism.

Michał Rygoł 4 months ago

Allow undoing a test step deletion

I've had this happen a few times when I wanted to delete a test step but didn't want to finally. It would be great if we can undo (at least) the last delete action. Using Ctrl+Z or a cancel deletion button somewhere.

Tegomass 4 months ago

Dump HTML of the page when the test failed

This option should be helpful, for example, when you want to diagnose why the given element selector doesn't work in the cloud.

Paweł Bylina 4 months ago