test(cli): verify malformed CSV rejection before reporting - #2118
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: LeanerCloud/cloud-commitments-cli/.coderabbit.yaml Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughCSV tests now use a shared fixture writer. A new test checks that malformed count and savings values produce line-2 CSV errors and do not create an output report. ChangesCSV test coverage
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to The added CSV checks match the actual error format and cover malformed inputs before report generation. No concrete merge-blocking risk is evident from the supplied change. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
…ration-regression
Adds CSV orchestration regression coverage for the parser fix already merged in #2114 (issue #1944).
The new table drives
runToolFromCSVwith fractional, suffixed, negative, and overflowing counts, plus currency-suffixed savings. It verifies parsing fails with line/column context before a purchase report is written. Existing CSV fixture creation is reused. Production behavior is unchanged.Verification:
3.7exited 1 with CSV line 2 / column 4 context and wrote no purchase report. No real purchases were made.Summary by CodeRabbit