We have been testing BugBug for several weeks now and have already created a large number of test cases for our Jira Forge application. One of the things we particularly like about BugBug is that you can create most test cases without having to dive into coding. While recording a test case, the browser extension captures everything you need. It automatically records the test steps and also allows you to add assets and validations that are important for proper test verification.

Before BugBug, we evaluated and used several other testing tools. BugBug offers an excellent cost–benefit ratio, and the roadmap looks very promising with many useful features planned. That said, the current feature set already works very well for us.

At the moment, we are in the process of building around 180 automated test cases for our Jira application, and they are running very reliably. To achieve this level of stability, we made some adjustments to our application so that it generates stable test IDs which we can consistently reference during testing.

What we also appreciate is that BugBug is easy to use for different types of users. Both our engineers and team members without a technical background are able to work with it and create test cases. You really don’t need advanced technical skills to get started.

In the past, manually running a full test suite could take us three to four days. With BugBug, we have reduced that effort to around 10% of the original time, and most of the work runs automatically in the background without requiring manual intervention.

Another major advantage for us is the webhook functionality. It allowed us to integrate BugBug smoothly with our Jira-based test case repository. We implemented the integration using n8n, and everything works seamlessly.

Overall, BugBug has significantly improved our testing workflow and efficiency. Review collected by and hosted on G2.com.

We also find the base pricing of BugBug quite reasonable. When using the cloud runners, we noticed that they can be slightly slower compared to running tests locally. However, the cloud runs are currently the most practical option when integrating tests into a CI/CD workflow.

Running additional parallel cloud tests is possible, but the pricing for multiple parallel runs can become relatively high. For this reason, we decided to run most of our tests in parallel across several local testing environments instead. This approach allows us to keep execution times short while maintaining a good balance between performance and cost. Review collected by and hosted on G2.com.

I’ve been using BugBug for about 2.5 years on the free plan, and it’s been a really solid experience.

The setup is straightforward: you record your test flow directly in the browser, mark important steps (like “change successful”), and that’s basically it. From there, you can rerun individual tests or all of them with just a few clicks. If a confirmation or another marked element is missing, the test fails, simple and effective. The automatic screenshots are also very helpful when debugging.

The biggest effort is at the beginning and whenever you change something significant (e.g. a modified submit button). Outside of that, the maintenance effort is minimal.

What I also appreciate is that the tool keeps improving over time. Useful features have been added gradually, like filters or the ability to continue execution even after a failed step. That shows active development and a good understanding of real-world usage.

For a free tool, the value is outstanding. It has already caught several issues before release while requiring very little ongoing time.

Overall: low effort, high impact. I’m genuinely impressed, especially considering it’s free. Review collected by and hosted on G2.com.

In the beginning, performance was quite slow on older hardware (in my case, an outdated Windows machine). On modern hardware with fast storage, this is no longer an issue.

Occasionally, tests fail without an obvious reason. The screenshot looks correct, and when I rerun the test, it passes. This can make debugging a bit unclear at times. Review collected by and hosted on G2.com.

Easy to use and learn, fast execution, suitable for local execution which doesn't require cloud Review collected by and hosted on G2.com.

Support: takes 24 hours to get the response; if you don't have paid subscription but would like to get one while trying to resolve blocking issues the support is not willing to come on the call and have a working session to resolve the roadblock

Features: image comparison, file comparison, open windows explored and select file for import, canvas testing, extended timeouts to allow longer analytics runs Review collected by and hosted on G2.com.

Ease of use. Very simple to add to Chrome and you're good-to-go.

Free for local use (v cloud-run tests). IF you make suggestioms, 'real people' comment and feedback v some bland 'thank you for your input' type replies. All the benefits of a smaller, younger and more responsive company Review collected by and hosted on G2.com.

I'd like to be able to check page <titles> and maybe other key non-display attributes. Have now learned that my grumble about wanting to run the same set of tests against the same system but in different environments, is covered by BugBug 'profiles', so looks like I simply need to learn more to get even more out of BugBug 🙂 Review collected by and hosted on G2.com.

BugBug is a highly intuitive tool that has helped us save a significant amount of time on regression testing. Thanks to BugBug, we have been able to shift from releasing quarterly to adopting a CI/CD approach. Review collected by and hosted on G2.com.

So far, I haven't encountered any downsides. Perhaps the only minor issue is that each run is limited to 30 minutes. However, this can be managed by splitting the run into separate segments. Review collected by and hosted on G2.com.

Easy to create tests.. Their reliability Review collected by and hosted on G2.com.

More information in the logs about the website errors Review collected by and hosted on G2.com.

It's super easy to use, even for people who weren't previously engaged in test automation activities. The UI, compared to the competitors, is super clear and let's you concentrate on building tests, rather than learning interface intricacies, from the get go.

Also - being able to do JS-based assertions/steps allows more tech-savvy users to overcome any software limitations.

POC implementation took us like a week, to be sure this is the right tool for us.

Support is also super responsive and helpful. Review collected by and hosted on G2.com.

There are some missing important features at the moment, like loops or conditional branching in test scenarios - so you can't build and maintain complex scenarios easily. Once those features are there, this product is top-tier. Review collected by and hosted on G2.com.

Ease of use : It's very simple to use. The UI is clear, so a beginner will quickly find everything he needs. Multiple features exists to create test quickly (record steps, stop the scenario in the middle of a test to edit steps and launch it again) Using components makes it easy to add modification to multiple tests by changing a parameter/a step in one place. You can also use premade variables or create your own + create steps using Javascript

Ease of implementation : Super simple, you had the credentials/info of the app/web page you want to test and you are ready to record tests.

Customer Support : They are very reactive. I had to contact them by mail 2 times, I had a reponse from them in less than 2 hours. And the reponse was helpful!

Ease of integration : our devs set up an integration of Bugbug in our Github action to launch a suite of test on branches and our staging environement. Review collected by and hosted on G2.com.

I would say the fact that there is no possibility to use components multiple times in one test (but it's on their roadmap).

Sometimes tests stop on a step for no reason, I have to delete the step and create exactly as the original one to make the test work again (very rare though)

I use the product since 1 month, I'm still curious about how fast they launch new features. Review collected by and hosted on G2.com.

1 YEAR LATER REVIEW UPDATE (2025): 4/5 -> 5/5

- So a bit more than one year later, our testsuite has grown and expanded greatly, and it's quite easy to manage and maintain it

- Onboarding new QA colleagues (with and without automation experience,) with the tool is a smooth process

- Customer support is constantly improving and being very prompt (at least on a paid subscription plan)

INITIAL POINTS (2024):

- Most comprehensive no-code QA automation tool, comes as a "kit" ready to use "out of the box": no need to bother with setting up virtual machines of your own, you can run tests locally on your machine or in the cloud on BugBug infrastracture

- Ease of use for both QA and managers

- Easy to ramp-up and understand for manual testers looking to dip their feet in automation

- A decent number of implemented features and more incoming

- We use it non-stop for smoketests and E2E tests foro ur web based product

- Comprehensive and easy to follow documentation

- Quite quick and easy to set up

- Useful list of integrations (Slack, Zapier, GitHub)

- Active and helpful customer support

- Good enough transparency on upcoming features

- Dedicated place to gather user feedback, improvements or feature ideas

- Quick solution for cutting down on execution time as project grows: option to buy extended infrastracture to run multiple tests in "parallel" (which is tempting especially for QA testers without automation experience, throwing more resources at the thing is an option, but so is optimising the test automation strategy and mindset of recording steps) Review collected by and hosted on G2.com.

1 YEAR LATER REVIEW UPDATE (2025):

My biggest gripe as seen in my initial points was the ability to control recording functionality, which is now completely solved thanks to a revamped flow which allows me to start a recording session, and use it continuously by pausing recording mode and manipulate steps at any moment, with ability to resume the test at any location. This has reduced the time spent on test writting and fixing by half at least, since I don't need to keep running a test from scratch after each small update. I think this is a unique and intuitive function that I haven't seen on any other established automation framework before, and really sets BugBug appart from them.

Points that are still there at present time:

- Lack of conditional steps, still need to fallback to custom javascript steps for this

- Over the last year, our variables number has increased, and the dedicated section for them is still difficult to maintain and organize (for example in folders or categories)

- I got used to reporting issues with the software using their support email, but I still wished there was a dedicated place to report issues from inside their webpage

- Ability to use a component multiple times in a test is currently a work in progress and hopefully should be launched soon

INITIAL POINTS (2024):

- Wish I could have more control during recording of a test, such as where to record a step

- The pause/resume during recording is a bit hit or miss and not very smooth

- A bit cumbersome to check if a fix for a long test is working, because there is no way to specificy the location from where the test can start execution (if a test takes 7 minutes, and something fails around minute 6, after fixing you have to run the test from the beginning, instead of clicking "execute from here" from a certain section of the test for example)

- Lack of conditional steps (if, when, while)

- I see the difficulty of keeping track of test variables (and not project variables) increasing the more tests you implement: and this is a downside compared to code-based automation tools (such as Cypress or Playwright)

- The tool does not have an equivalent to a "function" in programming: the closest is the concept of a test "component" aka a block of tests, but it can only be used once per test (at the moment)

- Lack of a place to report bugs with the tool (handled by emailing bugbug support)

- More control over parallel runs: as it is, it's a setting toggle that can be true or false at a testsuite level Review collected by and hosted on G2.com.

1.BugBug's interface is intuitive and easy to navigate, making it accessible even for those new to automated testing.

2.No Coding Required for BugBug it Allows non-developers to create and run tests without needing to write any code.

3.Quick Setup,Tests can be set up quickly, which is ideal for smaller projects or teams with limited time.

4.BugBug had Record and Playback feature to simplifies the test creation process by allowing users to record their actions and replay them.

5. It is a cloud-based tool, BugBug doesn't require any local setup or installation, which can save time and resources.

6.Integration with CI/CD, BugBug can be integrated into CI/CD pipelines, automating tests as part of the deployment process.

7.Fast Execution,Tests execute quickly, allowing for rapid feedback during the development process.

8.Browser Extension,The BugBug browser extension enhances usability by enabling test recording directly within the browser. Review collected by and hosted on G2.com.

1.Limited support for complex test scenarios.

2.No cross-browser testing capabilities.

3.Dynamic content handling is unreliable.

4.Lacks advanced customization options.

5.Limited integrations with other tools.

6.Assertions are not flexible enough.

7.Test data reuse is challenging.

8.Limited community support for troubleshooting. Review collected by and hosted on G2.com.