Skip to content

Conversation

@guiandmag
Copy link
Contributor

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 x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in 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.

  • I have read the CONTRIBUTING doc
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

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...

- Add notHaveSimpleName, notHaveSimpleNameMatching methods
- Add notHaveSimpleNameEndingWith, notHaveSimpleNameStartingWith
- Add notResideInPackage as alias for resideOutsideOfPackage
- Fix TSClass constructor calls in tests to use object interface
- Remove invalid exports property from TSClass test mocks
- Add proper location property to TSClass test objects
- Add detailed code analysis report with architecture review
- Document current coverage status (29.77%)
- Create 4-phase plan to reach 80% coverage
- Provide detailed test implementation guidelines
- Estimate 72 hours to complete all phases
- Include module-by-module test specifications
- Fix pattern matching test to expect subpackage matching
- Add proper cleanup handling for performance tests
- Adjust timeline test expectations for edge cases
…ules

- Add ErrorHandler, ProgressBar, WatchMode tests for CLI module
- Add HtmlReportGenerator, JsonReportGenerator, JUnitReportGenerator,
  MarkdownReportGenerator, ReportManager tests for Reports module
- Add SuggestionEngine, ViolationAnalyzer tests for Analysis module
- Tests cover core functionality and edge cases
- Designed to improve code coverage toward 80% target
- ErrorHandler: Use parseError() then formatError() pattern
- ErrorHandler: Test with ErrorType enum instead of string literals
- WatchMode: Remove invalid 'exclude' property from ArchUnitConfig mock
- All tests now compile and pass successfully
@guiandmag guiandmag self-assigned this Nov 18, 2025
@guiandmag guiandmag merged commit 7b6ba3c into master Nov 18, 2025
1 of 16 checks passed
@guiandmag guiandmag deleted the claude/code-analysis-review-01XV7WenRRVtxEVNsk8ikH2W branch November 18, 2025 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants