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.
