Execute your test specifications with browser automation
--headless
)Command | Description | Example |
---|---|---|
bugster run | Run all available tests | bugster run |
bugster run auth/ | Run tests in specific directory | bugster run auth/ |
bugster run --headless | Run without browser UI | bugster run --headless |
bugster run --parallel 5 | Run up to 5 tests concurrently | bugster run --parallel 5 |
bugster run --only-affected | Run only tests for changed files | bugster run --only-affected |
Flag | Description | Example |
---|---|---|
--headless | Run tests in headless mode (no browser UI) | --headless |
--silent | Run in silent mode (less verbose output) | --silent |
--verbose | Enable verbose output for debugging | --verbose |
--parallel | Maximum number of concurrent tests (default: 3) | --parallel 8 |
--max-concurrent | Alias for —parallel | --max-concurrent 5 |
--limit | Maximum number of tests to run | --limit 10 |
--browser | Browser to use for tests | --browser chromium |
Flag | Description | Example |
---|---|---|
--only-affected | Only run tests for affected files/directories | --only-affected |
--base-url | Override base URL from config | --base-url https://staging.myapp.com |
Flag | Description | Example |
---|---|---|
--output | Save test results to JSON file | --output results.json |
--stream-results | Stream results to dashboard (default: true) | --stream-results |
--no-stream-results | Disable streaming to dashboard | --no-stream-results |
Use Case | Command | Description |
---|---|---|
Local development | bugster run | Run all tests with browser visible |
CI/CD pipeline | bugster run --headless --stream-results | Automated testing in CI |
Quick validation | bugster run --limit 5 --parallel 3 | Run subset of tests quickly |
Staging testing | bugster run --base-url https://staging.app.com | Test against staging environment |
Debugging | bugster run auth/ --verbose | Debug specific test category |
Performance testing | bugster run --parallel 10 --headless | Maximum speed execution |
--only-affected
in PR workflows to test only changed functionality--parallel
significantly speeds up execution but uses more resources--output
is useful for generating test reports in CI/CD