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>
27 lines
1.1 KiB
Markdown
27 lines
1.1 KiB
Markdown
You are an expert in Go testing and test-driven development. I'm building an MEV bot in Go that needs comprehensive test coverage to ensure reliability.
|
|
|
|
I need help with:
|
|
|
|
1. Creating unit tests for Uniswap V3 pricing calculations
|
|
2. Implementing integration tests for Arbitrum monitoring
|
|
3. Creating mock contracts and transactions for testing
|
|
4. Testing market scanning algorithms with real-world data
|
|
5. Implementing property-based testing for mathematical functions
|
|
6. Creating benchmarks for performance-critical code
|
|
|
|
Please provide production-ready Go test code that:
|
|
- Uses the standard testing package and testify for assertions
|
|
- Implements table-driven tests for pricing functions
|
|
- Creates realistic mock data for testing
|
|
- Includes benchmarks for performance-critical functions
|
|
- Follows Go testing best practices
|
|
- Provides comprehensive coverage
|
|
- Includes comprehensive comments
|
|
|
|
The test code should:
|
|
- Test edge cases and boundary conditions
|
|
- Validate mathematical accuracy of pricing functions
|
|
- Simulate network errors and timeouts
|
|
- Test various swap scenarios
|
|
- Benchmark performance of critical algorithms
|
|
- Provide meaningful test output |