Claude/improve test coverage 01 hgp z txwitcei s yx txb732 c #37
+1,783
−145
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
….test.ts - Fix violation object structure (add 'rule' property, use Severity enum) - Fix method calls to use correct fluent API methods - Fix report generator calls to include required options parameter - Add missing imports (Severity, ReportFormat) - Remove tests for non-existent methods - Fix ViolationFormatter static method usage
- Fix Markdown report title expectation (use actual title from generator) - Fix RuleComposer.not test expectation (invert logic correctly) - Fix Performance test cleanup (use rmSync instead of rmdirSync) - All 299 tests now pass successfully
- Document current coverage: 47.45% lines - Define target: 80% code coverage - Create 4-phase implementation plan - Prioritize modules by impact and effort - Estimate 2-3 weeks to reach target - Provide test quality standards and best practices
- ErrorHandler.test.ts: 45 tests, 100% coverage - All error types (config, filesystem, git, analysis, validation, unknown) - Error formatting with and without colors - Violations summary and individual formatting - Path shortening and grouping - Factory functions - ProgressBar.test.ts: 45 tests, comprehensive coverage - ProgressBar: constructor, update, increment, complete, ETA, rendering - Spinner: start, stop, update, animation frames - MultiProgressBar: add, update, increment, complete, completeAll Total: 90 new comprehensive tests ErrorHandler coverage: 100% ProgressBar coverage: ~90%+ CLI module coverage improved from 0-40% to 46%+
guiandmag
deleted the
claude/improve-test-coverage-01HgpZTxwitceiSYxTXB732C
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to ArchUnitNode?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...