Skip to main content
Goal: 3-5 critical flows tested. Running locally. Ready for CI.

Step 1: Define Your Critical Paths

Get your team together for 30 minutes. Ask:
  1. What do users pay for? → #1 critical path
  2. What blocks users from value? → Usually auth
  3. What wakes you up at 3am? → That’s critical
Write down 3-5 flows. No more. If you can’t pick 5, pick 3.

Step 2: Setup Bugster

1

Install

See Installation Guide for troubleshooting.
2

Authenticate and initialize

See Auth and Init command reference.

Step 3: Configure Authentication

Create a test user in your app, then add credentials:
config.yaml
Store secrets in .env (add to .gitignore):
.env
See Credentials and Roles for multiple roles and advanced setup.

Step 4: Write Your First Test

Then: @bugster-generate Create a test for user loginSee Plugin Command for details.
Run it:
See Run Command for all options.

Step 5: Cover Critical Paths

Write one test per critical path. Organize in folders:

Checklist

  • 3-5 critical paths identified
  • Bugster installed and initialized
  • Test user created with credentials in .env
  • All critical path tests passing locally

What’s Next

CI Integration

Run tests on PRs

Configuration

Customize settings

Test Management

Expand coverage