> ## Documentation Index
> Fetch the complete documentation index at: https://www.bugzy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequently asked questions about Bugzy — capabilities, setup, pricing, security, and BYOT.

## Getting started

<AccordionGroup>
  <Accordion title="What is Bugzy?">
    Bugzy is a virtual QA teammate that joins your software development lifecycle. It extends your test coverage, verifies every code change, triages test failures, and collaborates with your team through Slack, Teams, and your issue tracker.
  </Accordion>

  <Accordion title="How long does setup take?">
    A few minutes. Sign up at [bugzy.ai](https://www.bugzy.ai), choose where Bugzy should communicate with your team, and connect GitHub for repository access. Project workspaces may also ask for an application URL and product context.
  </Accordion>

  <Accordion title="Do I need QA experience?">
    No. Bugzy operates autonomously. It generates test plans from your product description and application, writes Playwright test code, executes tests, and triages failures. Teams without dedicated QA engineers use Bugzy as their entire QA layer.
  </Accordion>

  <Accordion title="What types of applications does Bugzy support?">
    Any web application accessible via a URL. Bugzy runs a real Chromium browser against your application, so it works with any framework — React, Next.js, Vue, Angular, Rails, Django, or static sites. The only requirement is a reachable URL for the environment you want to test.
  </Accordion>
</AccordionGroup>

## Capabilities

<AccordionGroup>
  <Accordion title="How does Bugzy verify my code changes?">
    When a PR is opened or a deployment lands, Bugzy's verify-changes task runs relevant tests against the change. Results are posted as PR comments and GitHub check runs, so your team sees pass/fail status directly on the pull request.
  </Accordion>

  <Accordion title="Can Bugzy join my meetings?">
    Yes. Invite [notetaker@bugzy.ai](mailto:notetaker@bugzy.ai) to meetings (Zoom, Google Meet, Teams). Bugzy analyzes the transcript and proposes follow-up QA actions based on what was discussed.
  </Accordion>

  <Accordion title="Can Bugzy verify changes made by AI agents?">
    Yes. When an AI coding agent creates a PR and a preview is deployed, Bugzy tests the preview and posts results as a GitHub check run. This creates an automated QA gate for AI-generated code.
  </Accordion>

  <Accordion title="What happens when Bugzy gets a test result wrong?">
    Reply to the finding in Slack or Teams. Bugzy re-evaluates, updates its knowledge base, and adjusts future triage. Over time, false positives decrease as Bugzy learns from team feedback.
  </Accordion>

  <Accordion title="How do I know when Bugzy ships new features?">
    When we publish a new changelog entry, Bugzy posts a short summary in your connected Slack or Teams channel so you don't have to go looking for it. If you'd rather not be notified, you can mute the channel — the full changelog is always available at [bugzy.ai/changelog](https://www.bugzy.ai/changelog).
  </Accordion>
</AccordionGroup>

## BYOT (Bring Your Own Tests)

<AccordionGroup>
  <Accordion title="Can I use my existing test suite?">
    Yes. Connect your test repo, and Bugzy runs the explore-test-codebase task to learn your framework and patterns. It can then contribute new tests that match your conventions.
  </Accordion>

  <Accordion title="Does Bugzy work with my test management system?">
    Bugzy can integrate with external TMS platforms like Zephyr and TestRail. Test case management becomes API-driven instead of file-based.
  </Accordion>

  <Accordion title="Can I push CI results to Bugzy?">
    Yes. External CI pipelines can push results to Bugzy via webhook. Bugzy triages the results the same way it triages its own managed test runs.
  </Accordion>
</AccordionGroup>

## Pricing

<AccordionGroup>
  <Accordion title="How does pricing work?">
    Bugzy uses outcome-based pricing: you pay for **triages** and **test case creations**, not per test run, seat, or user. Test runs themselves are unlimited within your plan's managed run cap. Overages on triages and test cases are metered and invoiced automatically. See the [pricing page](/docs/resources/pricing) for tier details.
  </Accordion>

  <Accordion title="Is there a free trial?">
    Yes. Every team gets a 21-day Trial plan with 50 triages and 10 test case creations at no cost. No credit card is required to start. Upgrade when you need more capacity or when the trial period ends.
  </Accordion>

  <Accordion title="What counts as a triage?">
    A triage is counted each time Bugzy's AI classifies a test failure — determining whether it's a product bug or a test-level issue. Each unique failure classification within a test run counts as one triage.
  </Accordion>

  <Accordion title="What counts as a test case creation?">
    A test case creation is counted each time Bugzy generates a new Playwright test file and commits it to your repository. Modifications to existing tests (e.g., auto-fix retries) do not count as new creations.
  </Accordion>

  <Accordion title="What happens when I exceed my plan limit?">
    **Paid plans:** Overage charges apply automatically at per-unit rates (e.g., €5 per extra triage on Starter). Your test runs are never paused — Bugzy keeps working and overages appear on your next invoice.

    **Trial plan:** When you reach your trial limits (50 triages or 10 test cases) or the 21-day period expires, new executions are blocked until you upgrade.
  </Accordion>

  <Accordion title="Can I cancel anytime?">
    Yes. All plans are month-to-month with no long-term contracts. Cancel from your dashboard at any time — your plan remains active through the end of the current billing period with a "cancellation pending" status.
  </Accordion>
</AccordionGroup>

## Security

<AccordionGroup>
  <Accordion title="Where is my data stored?">
    All data is processed and stored in EU-only infrastructure. The database runs on Supabase (PostgreSQL) with encryption at rest. Secrets and credentials are encrypted using Google Cloud KMS. See the [security page](/docs/security) for full details.
  </Accordion>

  <Accordion title="Does Bugzy have access to my source code?">
    Bugzy accesses your repository via GitHub OAuth with scoped permissions — specifically, repository contents (read/write for test files), webhooks, and PR comments. Generated tests are committed to a separate test repository, not your main codebase.
  </Accordion>

  <Accordion title="Is Bugzy GDPR compliant?">
    Yes. Bugzy is fully compliant with GDPR (Articles 5-34) and the Bulgarian Personal Data Protection Act (PDPA). A Data Processing Agreement (DPA) is available at [bugzy.ai/legal/dpa](https://www.bugzy.ai/legal/dpa). Contact [privacy@bugzy.ai](mailto:privacy@bugzy.ai) for data subject requests.
  </Accordion>

  <Accordion title="How are credentials handled?">
    Credentials and secrets are encrypted using Google Cloud KMS and stored in Supabase with Row Level Security. At runtime, secrets are injected into ephemeral Cloud Run containers that are destroyed after each task execution — no persistent state remains.
  </Accordion>
</AccordionGroup>

## Technical

<AccordionGroup>
  <Accordion title="What testing framework does Bugzy use?">
    Playwright with TypeScript. Bugzy generates standard `@playwright/test` scripts that run in Chromium. Since the tests are regular Playwright code, they are portable and can run in your own CI pipeline as well.
  </Accordion>

  <Accordion title="Can I customize generated tests?">
    Yes. Generated tests are standard Playwright TypeScript files committed to your repository. You can modify selectors, add assertions, adjust timeouts, or restructure test suites. Bugzy respects your changes on subsequent runs.
  </Accordion>

  <Accordion title="How does Bugzy handle flaky tests?">
    Bugzy's AI triage classifies each failure. Test-level issues (broken selectors, timing problems) are auto-fixed with up to 3 retry attempts. Genuine product bugs are filed separately to your issue tracker. The self-improvement engine tracks disputed findings and adjusts classification over time.
  </Accordion>

  <Accordion title="Can I run tests on a schedule?">
    Yes. Configure cron schedules from the Bugzy dashboard to run tests at any interval — hourly, daily, weekly, or custom. Scheduled runs execute the full test cycle and report results through your configured integrations.
  </Accordion>

  <Accordion title="What triggers can start a test run?">
    Multiple triggers are supported:

    * **GitHub events** — pull requests, pushes, or deployments
    * **Scheduled cron** — configurable from the dashboard
    * **Messaging** — Slack or Microsoft Teams messages
    * **Manual** — trigger directly from the Bugzy dashboard
  </Accordion>

  <Accordion title="Do I need to write any test code?">
    No. Bugzy generates standard Playwright TypeScript tests and commits them to your repository. However, if you have existing tests (BYOT), Bugzy works with those too — learning your patterns and contributing new tests that match your conventions.
  </Accordion>
</AccordionGroup>