Name: update_rules_testing
Author: YousufJamal05

Prompt file imported from YousufJamal05/khelkood (.cursor/commands/update_rules_testing.md). Copyright stays with the author.

Update Rules Testing

This command analyzes the current Firebase Security Rules and updates the rules_testing/ test suite to ensure comprehensive coverage and alignment with the latest rule changes.

Instructions

The command will automatically:

Analyze Current Rules: Parse firestore.rules, storage.rules, and database.rules.json to understand the current security model
Identify Missing Tests: Compare existing test coverage against current rules to find gaps
Update Test Files: Modify or create test files to cover all rule scenarios
Validate Test Structure: Ensure tests follow the established patterns and use proper helpers
Update Documentation: Refresh README files with current test coverage information

What Gets Updated

Firestore Rules Testing

Collections: users, brands, brandApprovals, items, categories, notifications
Subcollections: questionnaireAnswers under users
Helper Functions: isAuthenticated(), isSuperAdmin(), isBrandAdmin(), isApprovedBrandAdmin(), isOwner(), isBrandOwner()
Access Patterns: Read, write, update, delete operations for each role

Storage Rules Testing

User Images: /images/users/{userId}/{fileName} with customer role validation
Brand Images: /images/brands/{brandId}/{fileName} with brand admin role validation
File Validation: Image type checking (jpeg, jpg, png, webp) and 2MB size limit
Access Patterns: Read, write, delete operations with proper authentication

Database Rules Testing

Collections: users, brands, brandApprovals, items, categories, notifications
Subcollections: questionnaireAnswers under users
Completion Flag Protection: Prevents client-side manipulation of hasCompletedQuestionnaire
Role-Based Access: Super admin, brand admin, approved brand admin permissions

Test Coverage Areas

User Roles Tested

Super Admins: Full access to all collections, can write categories
Brand Admins: Access to their own brand data and approval requests (read-only)
Approved Brand Admins: Access to items and categories for content management
Regular Users: Access to their own user data and notifications (read-only)
Unauthenticated Users: Denied access to all protected resources

Security Scenarios

Authentication: Valid vs invalid user tokens
Authorization: Role-based access control
Data Isolation: Users can only access their own data
File Validation: Type and size restrictions for uploads
Completion Flag Protection: Prevents client-side manipulation
Cross-User Access: Prevents accessing other users' data

Expected Output

The command will:

Update Existing Tests: Modify current test files to match rule changes
Add Missing Tests: Create new test cases for uncovered scenarios
Fix Test Data: Update test helpers and data factories
Validate Coverage: Ensure 100% rule coverage across all services
Update Reports: Refresh test documentation and coverage reports

Usage

Type /update_rules_testing in Cursor chat to automatically update the entire test suite based on current Firebase rules.

Integration Points

The command automatically integrates with:

Existing Test Helpers: Uses test-helpers.ts for consistent test data
TSCommon Package: Leverages real enums and constants from the common package
Mocha Test Framework: Maintains compatibility with current test structure
Firebase Emulators: Ensures tests work with local development environment
Mochawesome Reports: Updates test reporting and coverage documentation

Quality Assurance

All updated tests will:

✅ Follow Established Patterns: Use existing test structure and helpers
✅ Maintain Type Safety: Use proper TypeScript interfaces and types
✅ Include Proper Documentation: JSDoc comments for all test functions
✅ Use Real Data: Leverage TSCommon enums and constants
✅ Ensure Cleanup: Proper test isolation and data cleanup
✅ Pass Linting: Follow project coding standards
✅ Generate Reports: Beautiful HTML test execution reports

Smart Features

The command automatically:

Detects Rule Changes: Compares current rules against existing tests
Identifies Gaps: Finds missing test coverage for new or modified rules
Preserves Working Tests: Only updates tests that need changes
Maintains Consistency: Ensures all tests follow the same patterns
Updates Documentation: Refreshes README files with current information
Validates Structure: Checks test file organization and naming

Examples

Complete Rules Update

/update_rules_testing

What happens:

Analyzes all three Firebase rules files
Updates 15+ test files across Firestore, Storage, and Database
Refreshes test helpers and data factories
Updates documentation and coverage reports
Ensures 100% rule coverage

Targeted Updates

The command can also handle specific scenarios:

New Collection Added: Automatically creates comprehensive tests
Rule Logic Changed: Updates existing tests to match new behavior
Helper Functions Added: Creates tests for new security functions
File Path Changes: Updates storage tests for new upload paths
Role Permissions Modified: Adjusts test expectations for role changes

Troubleshooting

Common Issues

Test Failures After Update
- Check Firebase emulator configuration
- Verify test data setup in helpers
- Ensure proper authentication contexts
Missing Test Coverage
- Review rule changes for new scenarios
- Check for edge cases in helper functions
- Validate role-based access patterns
Test Data Issues
- Update test helpers for new data structures
- Check TSCommon package for updated enums
- Verify storage path constants

Debug Mode

Run with debug output:

/update_rules_testing --debug

Success Metrics

After running the command, you should see:

✅ 100% Rule Coverage: All rules tested across all services
✅ All Tests Passing: 85+ tests with 95%+ success rate
✅ Updated Documentation: README files reflect current coverage
✅ Consistent Patterns: All tests follow established structure
✅ Real Data Usage: Tests use TSCommon enums and constants
✅ Beautiful Reports: HTML test execution reports generated

The command ensures your Firebase Security Rules testing suite stays up-to-date with the latest rule changes! 🚀

Install update_rules_testing and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Update Rules Testing This command analyzes the current Firebase Security Rules and updates the `rules_testing/` test suite to ensure comprehensive coverage and alignment with the latest rule changes. ## Instructions The command will automatically: 1. **Analyze Current Rules**: Parse `firestore.rules`, `storage.rules`, and `database.rules.json` to understand the current security model 2. **Identify Missing Tests**: Compare existing test coverage against current rules to find gaps 3. **Update Test Files**: Modify or create test files to cover all rule scenarios 4. **Validate Test Structure**: Ensure tests follow the established patterns and use proper helpers 5. **Update Documentation**: Refresh README files with current test coverage information ## What Gets Updated ### **Firestore Rules Testing** - **Collections**: `users`, `brands`, `brandApprovals`, `items`, `categories`, `notifications` - **Subcollections**: `questionnaireAnswers` under users - **Helper Functions**: `isAuthenticated()`, `isSuperAdmin()`, `isBrandAdmin()`, `isApprovedBrandAdmin()`, `isOwner()`, `isBrandOwner()` - **Access Patterns**: Read, write, update, delete operations for each role ### **Storage Rules Testing** - **User Images**: `/images/users/{userId}/{fileName}` with customer role validation - **Brand Images**: `/images/brands/{brandId}/{fileName}` with brand admin role validation - **File Validation**: Image type checking (jpeg, jpg, png, webp) and 2MB size limit - **Access Patterns**: Read, write, delete operations with proper authentication ### **Database Rules Testing** - **Collections**: `users`, `brands`, `brandApprovals`, `items`, `categories`, `notifications` - **Subcollections**: `questionnaireAnswers` under users - **Completion Flag Protection**: Prevents client-side manipulation of `hasCompletedQuestionnaire` - **Role-Based Access**: Super admin, brand admin, approved brand admin permissions ## Test Coverage Areas ### **User Roles Tested** - **Super Admins**: Full access to all collections, can write categories - **Brand Admins**: Access to their own brand data and approval requests (read-only) - **Approved Brand Admins**: Access to items and categories for content management - **Regular Users**: Access to their own user data and notifications (read-only) - **Unauthenticated Users**: Denied access to all protected resources ### **Security Scenarios** - **Authentication**: Valid vs invalid user tokens - **Authorization**: Role-based access control - **Data Isolation**: Users can only access their own data - **File Validation**: Type and size restrictions for uploads - **Completion Flag Protection**: Prevents client-side manipulation - **Cross-User Access**: Prevents accessing other users' data ## Expected Output The command will: 1. **Update Existing Tests**: Modify current test files to match rule changes 2. **Add Missing Tests**: Create new test cases for uncovered scenarios 3. **Fix Test Data**: Update test helpers and data factories 4. **Validate Coverage**: Ensure 100% rule coverage across all services 5. **Update Reports**: Refresh test documentation and coverage reports ## Usage Type `/update_rules_testing` in Cursor chat to automatically update the entire test suite based on current Firebase rules. ## Integration Points The command automatically integrates with: - **Existing Test Helpers**: Uses `test-helpers.ts` for consistent test data - **TSCommon Package**: Leverages real enums and constants from the common package - **Mocha Test Framework**: Maintains compatibility with current test structure - **Firebase Emulators**: Ensures tests work with local development environment - **Mochawesome Reports**: Updates test reporting and coverage documentation ## Quality Assurance All updated tests will: - ✅ **Follow Established Patterns**: Use existing test structure and helpers - ✅ **Maintain Type Safety**: Use proper TypeScript interfaces and types - ✅ **Include Proper Documentation**: JSDoc comments for all test functions - ✅ **Use Real Data**: Leverage TSCommon enums and constants - ✅ **Ensure Cleanup**: Proper test isolation and data cleanup - ✅ **Pass Linting**: Follow project coding standards - ✅ **Generate Reports**: Beautiful HTML test execution reports ## Smart Features The command automatically: - **Detects Rule Changes**: Compares current rules against existing tests - **Identifies Gaps**: Finds missing test coverage for new or modified rules - **Preserves Working Tests**: Only updates tests that need changes - **Maintains Consistency**: Ensures all tests follow the same patterns - **Updates Documentation**: Refreshes README files with current information - **Validates Structure**: Checks test file organization and naming ## Examples ### Complete Rules Update ```bash /update_rules_testing ``` **What happens:** - Analyzes all three Firebase rules files - Updates 15+ test files across Firestore, Storage, and Database - Refreshes test helpers and data factories - Updates documentation and coverage reports - Ensures 100% rule coverage ### Targeted Updates The command can also handle specific scenarios: - **New Collection Added**: Automatically creates comprehensive tests - **Rule Logic Changed**: Updates existing tests to match new behavior - **Helper Functions Added**: Creates tests for new security functions - **File Path Changes**: Updates storage tests for new upload paths - **Role Permissions Modified**: Adjusts test expectations for role changes ## Troubleshooting ### Common Issues 1. **Test Failures After Update** - Check Firebase emulator configuration - Verify test data setup in helpers - Ensure proper authentication contexts 2. **Missing Test Coverage** - Review rule changes for new scenarios - Check for edge cases in helper functions - Validate role-based access patterns 3. **Test Data Issues** - Update test helpers for new data structures - Check TSCommon package for updated enums - Verify storage path constants ### Debug Mode Run with debug output: ```bash /update_rules_testing --debug ``` ## Success Metrics After running the command, you should see: - ✅ **100% Rule Coverage**: All rules tested across all services - ✅ **All Tests Passing**: 85+ tests with 95%+ success rate - ✅ **Updated Documentation**: README files reflect current coverage - ✅ **Consistent Patterns**: All tests follow established structure - ✅ **Real Data Usage**: Tests use TSCommon enums and constants - ✅ **Beautiful Reports**: HTML test execution reports generated The command ensures your Firebase Security Rules testing suite stays up-to-date with the latest rule changes! 🚀

{ "prompt": "# Update Rules Testing\n\nThis command analyzes the current Firebase Security Rules and updates the `rules_testing/` test suite to ensure comprehensive coverage and alignment with the latest rule changes.\n\n## Instructions\n\nThe command will automatically:\n\n1. **Analyze Current Rules**: Parse `firestore.rules`, `storage.rules`, and `database.rules.json` to understand the current security model\n2. **Identify Missing Tests**: Compare existing test coverage against current rules to find gaps\n3. **Update Test Files**: Modify or create test files to cover all rule scenarios\n4. **Validate Test Structure**: Ensure tests follow the established patterns and use proper helpers\n5. **Update Documentation**: Refresh README files with current test coverage information\n\n## What Gets Updated\n\n### **Firestore Rules Testing**\n\n- **Collections**: `users`, `brands`, `brandApprovals`, `items`, `categories`, `notifications`\n- **Subcollections**: `questionnaireAnswers` under users\n- **Helper Functions**: `isAuthenticated()`, `isSuperAdmin()`, `isBrandAdmin()`, `isApprovedBrandAdmin()`, `isOwner()`, `isBrandOwner()`\n- **Access Patterns**: Read, write, update, delete operations for each role\n\n### **Storage Rules Testing**\n\n- **User Images**: `/images/users/{userId}/{fileName}` with customer role validation\n- **Brand Images**: `/images/brands/{brandId}/{fileName}` with brand admin role validation\n- **File Validation**: Image type checking (jpeg, jpg, png, webp) and 2MB size limit\n- **Access Patterns**: Read, write, delete operations with proper authentication\n\n### **Database Rules Testing**\n\n- **Collections**: `users`, `brands`, `brandApprovals`, `items`, `categories`, `notifications`\n- **Subcollections**: `questionnaireAnswers` under users\n- **Completion Flag Protection**: Prevents client-side manipulation of `hasCompletedQuestionnaire`\n- **Role-Based Access**: Super admin, brand admin, approved brand admin permissions\n\n## Test Coverage Areas\n\n### **User Roles Tested**\n\n- **Super Admins**: Full access to all collections, can write categories\n- **Brand Admins**: Access to their own brand data and approval requests (read-only)\n- **Approved Brand Admins**: Access to items and categories for content management\n- **Regular Users**: Access to their own user data and notifications (read-only)\n- **Unauthenticated Users**: Denied access to all protected resources\n\n### **Security Scenarios**\n\n- **Authentication**: Valid vs invalid user tokens\n- **Authorization**: Role-based access control\n- **Data Isolation**: Users can only access their own data\n- **File Validation**: Type and size restrictions for uploads\n- **Completion Flag Protection**: Prevents client-side manipulation\n- **Cross-User Access**: Prevents accessing other users' data\n\n## Expected Output\n\nThe command will:\n\n1. **Update Existing Tests**: Modify current test files to match rule changes\n2. **Add Missing Tests**: Create new test cases for uncovered scenarios\n3. **Fix Test Data**: Update test helpers and data factories\n4. **Validate Coverage**: Ensure 100% rule coverage across all services\n5. **Update Reports**: Refresh test documentation and coverage reports\n\n## Usage\n\nType `/update_rules_testing` in Cursor chat to automatically update the entire test suite based on current Firebase rules.\n\n## Integration Points\n\nThe command automatically integrates with:\n\n- **Existing Test Helpers**: Uses `test-helpers.ts` for consistent test data\n- **TSCommon Package**: Leverages real enums and constants from the common package\n- **Mocha Test Framework**: Maintains compatibility with current test structure\n- **Firebase Emulators**: Ensures tests work with local development environment\n- **Mochawesome Reports**: Updates test reporting and coverage documentation\n\n## Quality Assurance\n\nAll updated tests will:\n\n- ✅ **Follow Established Patterns**: Use existing test structure and helpers\n- ✅ **Maintain Type Safety**: Use proper TypeScript interfaces and types\n- ✅ **Include Proper Documentation**: JSDoc comments for all test functions\n- ✅ **Use Real Data**: Leverage TSCommon enums and constants\n- ✅ **Ensure Cleanup**: Proper test isolation and data cleanup\n- ✅ **Pass Linting**: Follow project coding standards\n- ✅ **Generate Reports**: Beautiful HTML test execution reports\n\n## Smart Features\n\nThe command automatically:\n\n- **Detects Rule Changes**: Compares current rules against existing tests\n- **Identifies Gaps**: Finds missing test coverage for new or modified rules\n- **Preserves Working Tests**: Only updates tests that need changes\n- **Maintains Consistency**: Ensures all tests follow the same patterns\n- **Updates Documentation**: Refreshes README files with current information\n- **Validates Structure**: Checks test file organization and naming\n\n## Examples\n\n### Complete Rules Update\n\n```bash\n/update_rules_testing\n```\n\n**What happens:**\n\n- Analyzes all three Firebase rules files\n- Updates 15+ test files across Firestore, Storage, and Database\n- Refreshes test helpers and data factories\n- Updates documentation and coverage reports\n- Ensures 100% rule coverage\n\n### Targeted Updates\n\nThe command can also handle specific scenarios:\n\n- **New Collection Added**: Automatically creates comprehensive tests\n- **Rule Logic Changed**: Updates existing tests to match new behavior\n- **Helper Functions Added**: Creates tests for new security functions\n- **File Path Changes**: Updates storage tests for new upload paths\n- **Role Permissions Modified**: Adjusts test expectations for role changes\n\n## Troubleshooting\n\n### Common Issues\n\n1. **Test Failures After Update**\n - Check Firebase emulator configuration\n - Verify test data setup in helpers\n - Ensure proper authentication contexts\n\n2. **Missing Test Coverage**\n - Review rule changes for new scenarios\n - Check for edge cases in helper functions\n - Validate role-based access patterns\n\n3. **Test Data Issues**\n - Update test helpers for new data structures\n - Check TSCommon package for updated enums\n - Verify storage path constants\n\n### Debug Mode\n\nRun with debug output:\n\n```bash\n/update_rules_testing --debug\n```\n\n## Success Metrics\n\nAfter running the command, you should see:\n\n- ✅ **100% Rule Coverage**: All rules tested across all services\n- ✅ **All Tests Passing**: 85+ tests with 95%+ success rate\n- ✅ **Updated Documentation**: README files reflect current coverage\n- ✅ **Consistent Patterns**: All tests follow established structure\n- ✅ **Real Data Usage**: Tests use TSCommon enums and constants\n- ✅ **Beautiful Reports**: HTML test execution reports generated\n\nThe command ensures your Firebase Security Rules testing suite stays up-to-date with the latest rule changes! 🚀", "variables": [], "notes": "This command analyzes the current Firebase Security Rules and updates the `rules_testing/` test suite to ensure comprehensive coverage and alignment with the latest rule changes.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/YousufJamal05/khelkood", "path": ".cursor/commands/update_rules_testing.md", "ref": "55d43a307ec15d4bc54928a65e3533e13886a2e5", "url": "https://github.com/YousufJamal05/khelkood/blob/55d43a307ec15d4bc54928a65e3533e13886a2e5/.cursor/commands/update_rules_testing.md", "key": "YousufJamal05/khelkood/.cursor/commands/update_rules_testing.md" } } }

update_rules_testing

About