BugBug review

BugBug is a no-code and AI-assisted tool for creating and running end-to-end and regression tests for web apps and websites. You can record browser flows visually or create tests with AI, then run them locally or in BugBug’s cloud.

The product covers more than test creation. BugBug says teams can connect AI agents through MCP to plan, create, maintain, and run tests. Reusable components help reduce repetition, while YAML import and export lets teams review, edit, back up, and version-control tests as text. Cloud runs can be scheduled or triggered from CI/CD, and email or Slack alerts can flag failures in critical flows.

The practical distinction is that BugBug offers local testing as well as cloud execution, but the Free plan includes local testing only. Cloud test runs start with the paid plans.

BugBug’s clearest strength is giving teams several ways to build and maintain tests without making every task a coding project. A visual recorder can turn browser flows into tests, while AI workflows offer another route for planning and maintaining coverage. Components can cut down on repeated setup across tests.

The workflow also has useful handoffs for teams that want more control: YAML import and export supports review and version control, and cloud runs can be scheduled or triggered from CI/CD. Email and Slack failure alerts help surface problems in critical flows. These features make BugBug relevant to teams that want no-code authoring but still need tests to fit into a broader QA process.

According to the published pricing details, Core includes unlimited cloud runs and unlimited test suites for $99 per month on annual billing, with three users, three projects, and 50 tests. Pro removes the listed caps on users, projects, and tests for $189 per month on annual billing. One Spanish-language Reddit commenter said the free version was fast and convincing, though that is a single anecdote, not much evidence of broader user experience.

The main pricing catch is the test cap on Core: $99 per month on annual billing buys room for 50 tests, not unlimited test volume. Teams that exceed that cap need to consider Pro at $189 per month on annual billing, which includes unlimited tests, users, and projects. The listed rates are annual-billing prices; monthly-billing prices are not published. Prices exclude VAT.

Free is tightly limited to local testing, one user, one project, four test suites, and 15 tests. That makes it useful for trying the workflow, but it does not include cloud runs. BugBug also lists a 14-day free trial, without specifying in the published pricing details which plan or features it covers. Business includes unlimited tests, users, projects, suites, and cloud runs, but its price is not published. A dedicated IP is a separate $50-per-month add-on. Teams should check their likely test count and billing preference before treating the entry price as their actual cost.

BugBug has a free plan for local testing, but it is capped at 15 tests, four suites, one user and one project. Cloud runs start with Core: $99 per month on annual billing, with 50 tests, three users and three projects. That makes Core a fit only if those limits work for your team.

Pro costs $189 per month on annual billing—$90 more than Core—and removes the test, user and project caps. Both paid plans include unlimited cloud runs and test suites. Business also lists unlimited usage, but its price is not published, so larger teams need a quote to compare costs.

The listed paid rates are monthly equivalents on annual billing, with up to 17% savings; monthly billing prices are not published. Prices exclude VAT. A dedicated IP is an additional $50 per month. Check the limits before switching: exceeding Core’s 50-test cap means paying for Pro, not simply adding more tests.

BugBug supports YAML import and export, so teams can review, edit, back up and version-control tests in a human-readable format. That gives you an option for preserving BugBug tests, but the published information does not establish that tests from another product can be imported without changes. Treat a move from a different runner as a possible rebuild, and confirm compatibility before planning around a bulk transfer.

Before moving away, export the YAML and check whether your next tool can use it; export alone does not guarantee portability. Also account for plan limits: Core allows 50 tests, while Pro lists unlimited tests. The published product information includes no sourced Reddit reports about why users leave BugBug, so we can’t responsibly claim a recurring user-reported reason. The price jump from Core to Pro and the unpublished Business rate are clear points to evaluate, but they are not evidence of Reddit users’ reasons for switching.