experiments: Cursor rule for Cursor

Testing and Development Workflow

Guidelines for testing and development practices in the Rempts CLI framework.

Testing Framework

• Use Bun's built-in test runner with bun test
• Test files should have .test.ts suffix in test/ directories
• Use testing utilities from packages/test/ for CLI-specific testing

Test Structure

// Example test file structure
import { describe, it, expect } from 'bun:test'
import { testCommand } from '@reliverse/rempts-test'
import { myCommand } from '../src/commands/my-command.js'

describe('My Command', () => {
  it('should execute successfully', async () => {
    const result = await testCommand(myCommand, {
      flags: { input: 'test' }  // Note: use 'flags', not 'args'
    })
    
    expect(result.exitCode).toBe(0)
    expect(result.stdout).toContain('success')
  })
  
  it('should handle positional arguments', async () => {
    const result = await testCommand(myCommand, {
      flags: { verbose: true },
      args: ['file1.txt', 'file2.txt']  // 'args' is for positional arguments
    })
    
    expect(result.stdout).toContain('file1.txt')
  })
  
  it('should handle plugin context', async () => {
    const result = await testCommand(myCommand, {
      flags: { verbose: true },
      context: {
        store: {
          someData: 'test data'
        }
      }
    })
    
    expect(result.stdout).toContain('test data')
  })
})

Testing Patterns

• Unit tests: Test individual functions and classes
• Command tests: Use packages/test/src/test-command.ts for CLI testing
• Integration tests: Test complete workflows in packages/test/test/advanced-scenarios.test.ts

Development Commands

From the root directory:

• bun dev - Start development mode with watch
• bun test - Run all tests
• bun run build - Build all packages
• bun run clean - Clean build artifacts