Development Workflow Overview
1
Develop your feature
You just finished implementing a new checkout flow.
2
Quick validation
Test your new checkout flow immediately to catch obvious issues:
3
Break testing
The destructive agent tries to break your new checkout functionality, giving you issues if found:
4
Regression testing
Make sure your checkout changes didn’t break other flows:
Common Local Testing Scenarios
1. Quick Feature Validation
After implementing a new feature, quickly test it to ensure it works:Use
--only-affected
to run only tests related to your recent changes, saving time and credits during development.2. Comprehensive Regression Testing
Before committing major changes, run a broader test suite:3. Interactive Development Testing
When you want to watch tests run and debug issues:You might want to use
--headless
when first learning, but prefer headless mode for better concentration during development.Additional Testing Options
Destructive Agent
The agent tries to break your interface and reports issues:Natural Language Testing
Ask Bugster to test something specific using natural language:Next Steps
Advanced Configuration
Customize your config.yaml for optimal local development settings
Cursor Integration
Learn how to integrate Bugster with Cursor for AI-powered development
This workflow optimizes for fast feedback during development. For production testing strategies, see our CI/CD Integration Guide.