Skip to main content
This guide walks you through onboarding Bugzy as your virtual QA teammate. By the end, Bugzy will be exploring your application, generating a test plan, and setting up automated testing — or analyzing your existing test suite if you bring your own.

​
Prerequisites

  • A GitHub account with at least one web application repository
  • A deployed or publicly accessible URL for your application (localhost is not supported)
1

Create a project

Click New Project to start the onboarding wizard. Provide the project details:
  • Project name — a descriptive label (e.g., “Storzy E-Commerce”)
  • App URL — where your application is running (e.g., https://staging.storzy.com)
  • Login credentials — username and password for test access (stored securely)
  • What areas would you like to test? — describe which features and flows Bugzy should focus on (e.g., “checkout flow, login, user registration, search”). This field is required.
Then choose your testing mode:
  • Managed testing (default) — Bugzy generates tests from scratch based on your testing focus.
  • Bring your own tests — Toggle this on if you already have a test suite. Provide your GitHub repository URL and branch.
2

Set up communication

Choose how Bugzy should send test results and updates to your team:
  • Slack — Connect your workspace via OAuth, select a channel, and Bugzy sends a welcome message to verify everything works.
  • Microsoft Teams — Connect your workspace via OAuth.
  • Email — Add one or more email recipients. Bugzy sends a verification email to confirm delivery.
You must complete this step before proceeding — Bugzy needs a way to reach your team.
For Slack: after connecting, pick the channel where Bugzy should post. If the bot isn’t in the channel yet, you’ll be prompted to add it first.
3

Review and launch

Review your configuration — project details, credentials, testing focus, and communication setup. When ready, click Launch Bugzy.
  • Managed mode: Bugzy kicks off the onboard-testing task, which explores your application, generates a test plan, writes Playwright tests, executes them, and reports results.
  • BYOT mode: Bugzy kicks off the explore-test-codebase task, analyzing your test framework, coverage, and conventions.
Take a coffee and relax — Bugzy is working through it. You’ll be redirected to the activity page where you can watch progress in real time.

​
What happens during onboarding

Managed testing: Bugzy runs the onboard-testing task end-to-end — it explores your app with a real browser, generates a structured test plan, writes Playwright test scripts, executes them, triages any failures, and posts a summary to your connected channel. BYOT: Bugzy runs the explore-test-codebase task — it reads your repo’s CLAUDE.md, scans the test directory structure, identifies patterns and conventions, and builds a knowledge base so it can contribute tests that match your existing style.

​
What’s next

How it works

See how Bugzy participates in your development lifecycle.

Extend test coverage

Learn how Bugzy generates test plans and Playwright automation.