ceven

Bugbug

Triggers automated web tests on every deployment, parses failure logs to find the root cause, and notifies the engineering team when a critical regression is detected.

Try Bugbug in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Bugbug integration

    • Describe the outcome and Ceven picks the right Bugbug calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Bugbug data, across all 4 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Bugbug access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Bugbug, when, and on whose behalf.
    • The agent pauses and asks when Bugbug is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Bugbug.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Bugbug action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Bugbug, and when to use it.

Get test run details
Use this when you need the full execution log, status, and error messages for a specific test run to diagnose a failure.
List suites
Pull all available test suites to organize which groups of tests should run for a specific feature release.
List tests
Retrieve every single test case in the account to audit coverage or find a specific test by name.
Run test
Execute a specific test immediately. Use this to trigger smoke tests after a hotfix or to validate a bug fix.
Search tests
Query for tests based on keywords or tags to find all tests related to a specific page like checkout or login.
Get suite details
Pull the configuration and member tests of a specific suite to verify the test order.
Update test state
Change the active status of a test. Use this to disable flaky tests that are causing false positives in the pipeline.
List test runs
Pull a history of recent test executions to identify intermittent failures or performance degradation over time.
Trigger suite run
Start all tests within a specific suite. Use this for full regression passes before a major version release.
Get account info
Pull current plan limits and usage stats to ensure the agent does not exceed the monthly test run quota.
Filter failed runs
Search for only the test runs that ended in a failure state within a specific time window.
Export test results
Pull test run data into a format suitable for external reporting or compliance audits.

12 actions · scroll to see them all

Frequently asked questions

When a Bugbug test fails, Ceven does not just send a generic alert. The agent uses the Get test run details action to pull the specific error message and the step number where the failure occurred. It then analyzes the failure reason, such as a timeout or a missing element, and compares it to recent changes in your environment. If you have connected your version control system, Ceven can suggest which commit likely caused the break. The agent then packages this context into a ticket or message, ensuring the developer has the exact Bugbug run ID and a description of the failure without ever leaving their primary workspace.
Yes. When the agent calls the Run test action, it can pass specific configuration overrides for the browser, device, and viewport. This allows you to build workflows that run the same Bugbug test across Chrome, Firefox, and Safari in parallel. For example, you can set up a workflow where a successful run on Chrome triggers a secondary check on mobile viewports to ensure responsive design elements are still functioning. The agent collects the results from all these different environments and provides a unified summary of where the application passed or failed across the browser matrix.
Ceven is bound by the API rate limits and the plan quotas of your Bugbug account. A known quirk of the Bugbug API is that concurrent test runs are limited based on your subscription tier. If a workflow attempts to trigger too many suites at once, Bugbug may return a rate limit error. To handle this, Ceven implements a queuing system that staggers test executions. If the agent hits a hard limit, it will pause and retry the request using an exponential backoff strategy to ensure no tests are skipped while staying within the boundaries of your specific Bugbug pricing tier.
Ceven can dynamically inject variables into Bugbug tests at runtime. This is useful for testing different user accounts or environment URLs without creating multiple versions of the same test. Through the Run test action, the agent can override variables like usernames, passwords, or product IDs. For instance, a workflow can pull a fresh set of test credentials from a secure vault and pass them into the Bugbug execution. This ensures that your automated tests are using current data and can run across different staging and preview environments without manual updates to the test scripts.
Currently, Ceven focuses on the execution and analysis of tests rather than the creation of the tests themselves. Bugbug is designed as a low code visual recorder, so tests are best created using their point and click browser extension. Once you have recorded the test and saved it in your Bugbug account, Ceven takes over the operational side. The agent manages when those tests run, monitors the results, and handles the downstream communication. This separation allows you to use the best tool for recording while using Ceven to automate the actual testing lifecycle.
Yes, though it does so through the Ceven workflow scheduler rather than relying solely on internal Bugbug schedules. By using the Ceven scheduler, you can create complex dependencies. For example, you can tell the agent to run a Bugbug suite every morning at 8 AM, but only if the previous night's database migration was successful. If the migration failed, the agent can skip the tests and alert the DBA instead. This provides much finer grained control over your testing cadence than a simple timer, ensuring you are not wasting test credits on a known broken environment.
Ceven connects to Bugbug using secure API tokens that are encrypted at rest. We follow the principle of least privilege, meaning the agent only accesses the endpoints necessary to perform the actions you authorize in your workflows. All communication between Ceven and Bugbug happens over encrypted HTTPS connections. We do not store your test data or the results of your runs permanently; we pull them into the workflow context to perform analysis and then clear the temporary data. You can rotate your Bugbug API token at any time, which will immediately disconnect the agent until the new token is provided.
Flaky tests are a common pain point in web automation. Ceven helps by tracking the history of test runs over time. If the agent notices that a specific Bugbug test fails and then passes on a second attempt without any code changes, it flags that test as flaky. You can set up a workflow that automatically moves flaky tests into a separate suite or disables them using the Update test state action. This prevents false alarms from waking up your engineering team at night while still keeping a record of the instability so the QA team can investigate the underlying cause.

Alternatives to Bugbug

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

mabl logomablTestim logoTestimSelenium logoSelenium

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Bugbug and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free