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.

Easy to create tests.. Their reliability

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.