The bugster init command initializes Bugster CLI in your project, handles authentication, and configures your project settings.

The init command is the first step you must complete before using any other Bugster CLI features. It sets up authentication and creates your project configuration.

​
Basic Usage

bugster init

This command will guide you through:

  1. Authentication (if first time)
  2. Project configuration
  3. Credential setup (for authenticated apps)

​
Step-by-Step Process

1

Navigate to your project

Open your terminal and navigate to your Next.js project’s root directory:

cd your-nextjs-project
2

Run the init command

Execute the initialization command:

bugster init
3

API Key Authentication (First Time Only)

If it’s your first time using Bugster CLI, you’ll be prompted for your API key:

🔑 Paste your API key here: bugster_your_api_key_here

Get Your API Key

Find your API key in the Bugster Dashboard under Account Settings

4

Configure Project Settings

You’ll be prompted to configure your project:

Project Name

🏷️  Project name: my-awesome-app
Use your GitHub repository name for consistency

Base URL

🌐 Application URL: http://localhost:3000

Authentication Credentials (if your app requires login)

➕ Would you like to add custom login credentials? (y/n): y
👤 Credential name: admin
📧 Username/Email: test@example.com
🔒 Password: ********

​
What Gets Created

After running bugster init, the following structure is created in your project:

your-project/
├── .bugster/
   ├── config.yaml          # Project configuration
   └── tests/               # Generated test directory (created later)
└── .gitignore               # Updated with Bugster entries

​
Configuration File

The config.yaml file contains your project settings:

project_name: "My App"
project_id: "my-app-123456"
base_url: "http://localhost:3000"
credentials:
  - id: "admin"
    username: "admin@example.com"
    password: "admin123"

​
Configuration Options

​
Advanced Configuration

For advanced use cases, you can customize additional settings in your config.yaml file:

Advanced Configuration

Learn about advanced configuration options including Vercel protection bypass, always-run tests, and more

​
Troubleshooting

​
Next Steps

After successful initialization, you’re ready to:

Generate Tests

Create AI-powered test specifications from your codebase

GitHub Integration

Connect your repository for automated testing on pull requests

Advanced Configuration

Learn about advanced configuration options including Vercel protection bypass, always-run tests, and more