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
PriorityFlow TypeExample
P0Auth gateLogin, Signup
P0Core valueCreate project, Make purchase
P1ConversionUpgrade plan, Invite team
Write down 3-5 flows. No more. If you can’t pick 5, pick 3.

​
Step 2: Setup Bugster

1

Install

  • macOS / Linux
  • Windows
curl -sSL https://bugster.dev/install.sh | bash
See Installation Guide for troubleshooting.
2

Authenticate and initialize

bugster auth
bugster init
See Auth and Init command reference.

​
Step 3: Configure Authentication

Create a test user in your app, then add credentials:
config.yaml
credentials:
  - id: user
    username: ${BUGSTER_USERNAME}
    password: ${BUGSTER_PASSWORD}
Store secrets in .env (add to .gitignore):
.env
BUGSTER_USERNAME=[email protected]
BUGSTER_PASSWORD=TestPassword123!
See Credentials and Roles for multiple roles and advanced setup.

​
Step 4: Write Your First Test

  • AI Agent
  • Manual
bugster plugin --agent cursor  # or --agent claude
Then: @bugster-generate Create a test for user loginSee Plugin Command for details.
Run it: 
bugster run .bugster/tests/auth/login.yaml
See Run Command for all options.

​
Step 5: Cover Critical Paths

Write one test per critical path. Organize in folders: 
.bugster/tests/
├── auth/login.yaml
├── core/create-project.yaml
└── billing/upgrade-plan.yaml

bugster run  # Run all tests

​
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