Skip to main content
Transform Cursor into a Bugster expert that can both generate comprehensive test specifications and automatically validate your UI changes as you build.

​
Three Cursor Use Cases for Bugster

Bugster provides three specialized Cursor rules to enhance your development workflow:

Test Generation

Manual activation - Generate comprehensive test specifications following Bugster’s YAML structure and best practices.

Test Update

Manual activation - Update existing test specifications based on code changes and new requirements.

Quick Validation

Auto-activation - Automatically validate UI changes after modifying components or pages with a final E2E test.

​
Using Cursor with Bugster

Cursor rules provide persistent context about your Bugster project, ensuring consistent test generation and automatic validation that follows your standards and best practices.
  • Project rules are stored in your repository and shared with your team.
  • User rules apply to your personal Cursor environment.
We recommend creating project rules for your Bugster project so that all contributors generate tests following the same standards. Create rules files in the .cursor/rules directory of your project. See the Cursor Rules documentation for complete setup instructions.

​
Test Generation Rule

This rule provides Cursor with context to properly generate Bugster test specifications following the required YAML structure and best practices.

​
Installation

Install the official test generation rule using the Bugster CLI:
This installs bugster-generate.mdc in your .cursor/rules/ directory.
View the official rule: Cursor Test Generation Rule

​
How to Use

Reference the rule in your Cursor chat to activate it:

​
What It Does

  • Generates comprehensive test specifications in proper YAML format
  • Follows Bugster naming conventions and file structure
  • Creates tests in .bugster/tests/ with correct hierarchy
  • Validates all required fields are present
  • Limits generation to avoid test duplication
The rule automatically checks existing tests to avoid duplicates and follows your project’s file structure conventions.

​
Test Update Rule

This rule helps you update existing test specifications when your code changes or requirements evolve.

​
Installation

Install the official test update rule using the Bugster CLI:
This installs bugster-update.mdc in your .cursor/rules/ directory.
View the official rule: Cursor Test Update Rule

​
How to Use

Reference the rule in your Cursor chat to activate it:

​
What It Does

  • Updates existing test specifications to match code changes
  • Maintains test structure while adapting to new requirements
  • Preserves test intent while updating implementation details
  • Ensures tests stay synchronized with your codebase
  • Follows the same YAML standards as test generation
Use this rule after refactoring components or updating user flows to keep your test suite current without starting from scratch.

​
Quick Test Rule

This rule automatically validates your UI changes by running a comprehensive E2E test after you modify components or pages. It helps ensure your implementation meets user requirements.
File name suggestion: bugster-quick-test.mdc
E2E tests are slow (30-300 seconds). This rule is designed to run sparingly - only as final verification after code changes.
Add this rule as a .mdc file in the .cursor/rules directory of your project:

​
Combining All Rules

For optimal workflow, use all three rules together:
1

Setup

Install the official rules and add the quick test rule to your .cursor/rules directory:
Then add bugster-quick-test.mdc (see Quick Test Rule section above) for auto-validation.
2

Development Flow

  1. Build your feature as requested
  2. Quick Test rule automatically validates the implementation
  3. Use Test Generation rule to create comprehensive test suites
  4. Use Test Update rule when refactoring or updating features
3

Team Consistency

All three rules ensure team members follow the same Bugster standards and validation processes.
The plugin command installs both generation and update rules automatically. Add the quick validation rule manually for auto-testing after code changes.