BugBug Pricing Overview

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.