Vijay Janapa Reddi
|
c5389e9e47
|
docs: Add comprehensive integration testing rules
- Create focused integration testing rule (256 lines, under 500-line limit)
- Establish core principle: interface compatibility over functionality re-testing
- Define 4 integration test categories: Foundation, Architecture, Training, Inference
- Provide clear DO/DON'T examples with code snippets
- Document testing anti-patterns to avoid
- Include educational testing principles and workflow guidelines
- Reference 17 existing integration test files in tests/ directory
- Update rules README to include new integration-testing.md rule
|
2025-07-18 00:33:26 -04:00 |
|
Vijay Janapa Reddi
|
391b0a8999
|
Refactor rules into focused, non-redundant set
- Eliminate redundancy across rule files
- Keep all rules under 500 lines (largest is 187 lines)
- Create focused, actionable rules scoped to specific concerns
- Extract 'Real Data, Real Systems' principles to dedicated file
- Streamline testing patterns to core requirements only
- Fix corrupted development-workflow.mdc file
- Remove duplicate content between files
- Add comprehensive rules overview documentation
Rule organization:
- Core Context: ml-systems-course-context, tinytorch-project-structure, user-preferences
- Development Workflow: development-workflow, git-workflow, cli-patterns
- Module Development: module-development-best-practices, nbdev-educational-pattern, real-data-principles
- Testing: testing-patterns
Each rule is now focused, actionable, and composable without redundancy.
|
2025-07-11 22:51:49 -04:00 |
|