c54c569f30
Completed clean root directory structure: - Root now contains only: .git, .env, docs/, orig/ - Moved all remaining files and directories to orig/: - Config files (.claude, .dockerignore, .drone.yml, etc.) - All .env variants (except active .env) - Git config (.gitconfig, .github, .gitignore, etc.) - Tool configs (.golangci.yml, .revive.toml, etc.) - Documentation (*.md files, @prompts) - Build files (Dockerfiles, Makefile, go.mod, go.sum) - Docker compose files - All source directories (scripts, tests, tools, etc.) - Runtime directories (logs, monitoring, reports) - Dependency files (node_modules, lib, cache) - Special files (--delete) - Removed empty runtime directories (bin/, data/) V2 structure is now clean: - docs/planning/ - V2 planning documents - orig/ - Complete V1 codebase preserved - .env - Active environment config (not in git) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2.1 KiB
2.1 KiB
Write Comprehensive Tests
Write comprehensive tests for the following functionality: $ARGUMENTS
Testing Framework:
- Test Planning: Design test cases for all scenarios
- Unit Testing: Implement unit tests with high coverage
- Integration Testing: Create integration tests for component interactions
- Property-Based Testing: Implement property-based tests for mathematical functions
- Fuzz Testing: Add fuzz tests for edge cases
- Benchmark Testing: Create benchmarks for performance-critical code
Testing Standards:
- Coverage Targets: >90% for Go, >95% for Solidity, >85% for JavaScript
- Test Organization: Follow language-specific testing conventions
- Test Data: Use realistic test data and edge cases
- Test Documentation: Document test scenarios and expected outcomes
Language-Specific Testing:
Go Testing
// Unit tests with table-driven approach
func TestFunctionName(t *testing.T) {
tests := []struct {
name string
input InputType
expected OutputType
wantErr bool
}{
// Test cases
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
// Test implementation
})
}
}
Solidity Testing
// Property-based testing with Foundry
function testFuzz_ValidInputs_AlwaysWork(uint256 amount) public {
vm.assume(amount > 0 && amount < type(uint128).max);
// Test implementation
}
JavaScript Testing
// Vue component testing with Vitest
describe('ComponentName', () => {
it('should render correctly', () => {
// Test implementation
})
})
Test Categories:
- Happy Path: Tests for expected normal operation
- Edge Cases: Tests for boundary conditions
- Error Conditions: Tests for error handling
- Security: Tests for potential vulnerabilities
- Performance: Benchmarks for critical functions
Deliverables:
- Comprehensive test suite with high coverage
- Property-based tests for mathematical functions
- Fuzz tests for edge cases
- Benchmark tests for performance-critical code
- Test documentation and scenarios