Added
bugster generate --prompt
- Generate tests directly from natural language prompts without needing existing spec files
Added
- Optional
credential_id
field to the Test model to enhance test configuration capabilities
Changed
- Default maximum concurrent tests changed from 5 to 3 for better resource management
- Added
--quick
option to the prompt parameter in therun
command
Fixed
- Simplified log visibility condition in
should_show_detailed_logs
function for improved debugging experience
Added
bugster destructive --output
option to save results to a JSON file, enabling easier integration with other tools and workflowsbugster run --prompt
option for creating quick, on-the-fly tests without pre-existing spec files- PowerShell installer script for Bugster CLI on Windows
- Windows installation instructions to the documentation
Changed
- Enhanced PowerShell installer to automatically check for and install Node.js and npm if missing
Removed
- Legacy CI workflow configuration file
Changed
bugster config
command flags now uses separate flags:--bypass-protection-interactive
for guided setup and--bypass-protection-secret
for direct secret input
Added
- Credentials validation in
bugster init
- prevents empty username/password entries - Localhost reminder in
bugster run
- warns users to ensure app is running before tests - CI/CD integration warning in
bugster init
- clear instructions on which files to commit - Enhanced messaging system with proper console message methods
Changed
- Improved URL prompt in
bugster init
- clarifies localhost usage and CI/CD auto-changes - Better credentials explanation - explains when authentication gateway credentials are needed
- Config.yaml now includes commit reminder comment for CI/CD integration
Added
bugster config
command - Access and manipulate the data inside config.yaml to avoid human error--bypass-protection
flag: Guides users on how to get the x-vercel-bypass-secret by redirecting them with the Deeplink
bugster install
command - Handle outside integrations with your Bugster account for users who don’t want to switch context during setup--github
flag: Redirects users to the Github App Installation Link
Changed
- Destructive Agent Limits - Up to 4 as default, with future parametrization based on subscription tiers
- Prioritization of UI crashers instead of Form Destroyers (FD will run when all UI Crashers are ok)
Changed
- New architecture for
bugster destructive
unblocking longer executions
Added
- Initial monorepo support
- Works with most monorepo setups including basic Turborepo configurations
- Detects changes in individual apps within the monorepo
- Note: Currently does not track changes in shared packages (e.g., common components installed via pnpm in each app’s node_modules)
Changed
bugster generate
default settings - Can be executed multiple times without adding--force
explicitly- Improved test generation intelligence - Both
bugster generate
andbugster update
now analyze existing test specs context to avoid creating duplicate or similar tests
Changed
- Force chromium installation on install script
- Remove the question loop on credentials during
bugster init
Changed
- Enhanced
--page
flag inbugster generate
now accepts relative or absolute file paths instead of page folder names - Added validation for the
--page
flag to ensure provided paths exist, are files, and have valid JavaScript/TypeScript extensions (.js
,.jsx
,.ts
,.tsx
)
Added
--stream-results
as the default behaviour forbugster run
--max-concurrent = 5
as the default behaviour forbugster run
--page
flag forbugster generate
for spec generation of specific pages--count
option forbugster generate
to control the number of test specs generated per page (min: 1, max: 30)
Added
preferences
section to the configuration filealways_run
option to select up to 3 specs that will always run
Changed
- Improved
bugster generate
architecture resulting in a 30% speed increase
Added
- Vercel-bypass-automation support - You can now use the secret within Bugster config while keeping your branch protected
Added
bugster issues
command to get failed runs with debugging context from recent executionsbugster upgrade
command to update CLI to the latest version directly from the command line
Changed
- Improved specs generation algorithm for better coverage and more realistic test scenarios
Fixed
- Small bug in the console message during
bugster init
Added
--only-affected
flag forbugster run
to execute only specs affected by code changes--max-concurrent
flag forbugster run
supporting up to 5 parallel test executions- Component-level tracking for
bugster update
command - GitHub integration for running specs on Vercel preview deployments
- Cross-platform installer scripts for Windows, macOS, and Linux with automatic dependency management
Changed
- Enhanced
bugster update
command now works at component granularity instead of file level - Improved parallel test execution with better resource management
- Optimized change detection algorithm for more accurate affected test identification
- Rich console output with color-coded messages and progress indicators
- Enhanced error handling with detailed debugging information
Fixed
- Performance improvements for large codebases with many components
- Better handling of component dependency tracking
- Reduced false positives in change detection
Added
bugster sync
command to retrieve and manage test specs across different branchesbugster auth
command for secure API key management with GUI integrationbugster update
command to automatically update test specs when codebase changes- Project creation integration with Bugster GUI dashboard for execution tracking
- Branch-based specs synchronization
Changed
- Enhanced
bugster init
command now creates projects in the GUI dashboard
Fixed
- Authentication improvements
- Project initialization reliability
- Cross-branch synchronization edge cases
Added
- Initial CLI commands:
bugster init
,bugster generate
, andbugster run
- Next.js application support with automatic framework detection
- Test specs generation (up to 5 test specs per application)
- Basic test execution engine with browser automation
- Project configuration system with YAML-based config files
- Core specs format and parsing capabilities