All notable changes to Bugster CLI will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
bugster configcommand This command will be used to access and manipulate the data inside config.yaml ( so as to avoid human error)
Right now the only flag available is --bypass-protection. This will guide users on how to get the x-vercel-bypass-secret by re-directing them with the Deeplink cc: @giovaborgogno
bugster installcommand This command will be used to handle outside integrations with your Bugster account for users that dont want to switch context setting up the account ( especially during Manual Onboarding)
Right now the only flag available is --github. This will re-direct the user to the Github App Installation Link. I proposed to add a Terminal re-direction in further iterations after the installation process has been finished successfully.
- Destructive Agent Limits Up to 4 as default. Later on we can parametrize with the subscription tiers Prioritization of UI crashers instead of Form Destroyers ( FD will run when all UI Crashers are ok)
- Added
bugster authcommand for setting up or cleaning existing api key - Added
-- parallelforbugster runcommand. Accept both--paralleland--max-concurrent
- Changed max test limit to 10
- Added platform flags to
bugster initfor faster setup
- Added flags to
bugster initfor executing automatically.
- Patch update command.
- New architecture for
bugster destructiveunblocking longer executions.
- 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)
bugster generatedefault settings. You can execute it multiple times, without having to add --force explicitly.- Improved test generation intelligence: both
bugster generateandbugster updatenow analyze existing test specs context to avoid creating duplicate or similar tests
- Force chromium installation on install script
- Remove the question loop on credentials during
bugster init
- The
--pageflag inbugster generatenow accepts relative or absolute file paths instead of page folder names. This provides more flexibility and control over which pages are analyzed. - Added validation for the
--pageflag to ensure that provided paths exist, are files, and have valid JavaScript/TypeScript extensions (.js,.jsx,.ts,.tsx).
- Added
--stream-resultsas the default behaviour forbugster run - Added
--max-concurrent = 5as the default behaviour forbugster run - Added
--pagefor commandbugster generatefor spec generation of a specific page or set of pages. - Added
--countoption forbugster generateto control the number of test specs generated per page (min: 1, max: 30)
- Added Vercel protection bypass to
bugster destructive
- Added
run_idtobugster destructivefor test run association
- Added
bugster destructive, our new agent for raising bugs.
0.3.11 - 2025-06-25
- Added
preferencessection to the configuration file. - Added
always_runoption to select up to 3 specs that will always run.
0.3.10 - 2025-06-24
- Improved
bugster generatearchitecture, resulting in a 30% speed increase.
0.3.9 - 2025-06-23
- Added
vercel-bypass-automationsupport: you can now use the secret within Bugster config while keeping your branch protected
0.3.7 - 2025-06-19
- Enhanced
bugster generatespecs generation capacity up to 20 specs for comprehensive coverage
- Improved specs generation algorithm for better coverage and more realistic test scenarios
0.3.6 - 2025-06-19
bugster issuescommand to get failed runs with debugging context from recent executionsbugster upgradecommand to update CLI to the latest version directly from the command line
- Improved specs generation algorithm for better coverage and more realistic test scenarios
- Small bug of the console message during
bugster init
0.3.0 - 2025-06-13
--only-affectedflag forbugster runto execute only specs affected by code changes--max-concurrentflag forbugster runsupporting up to 5 parallel test executions- Component-level tracking for
bugster updatecommand - GitHub integration for running specs on Vercel preview deployments
- Cross-platform installer scripts for Windows, macOS, and Linux with automatic dependency management
- Enhanced
bugster updatecommand 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
- Performance improvements for large codebases with many components
- Better handling of component dependency tracking
- Reduced false positives in change detection
0.2.0 - 2025-06-06
bugster synccommand to retrieve and manage test specs across different branchesbugster authcommand for secure API key management with GUI integrationbugster updatecommand to automatically update test specs when codebase changes- Project creation integration with Bugster GUI dashboard for execution tracking
- Branch-based specs synchronization
- Enhanced
bugster initcommand now creates projects in the GUI dashboard
- Authentication improvements
- Project initialization reliability
- Cross-branch synchronization edge cases
0.1.0 - 2025-05-21
- 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