Increase AI server test coverage#4
Draft
roncodes wants to merge 43 commits into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This draft PR wires backend coverage reporting into the AI package CI and brings
./serverbackend coverage to 100%.Coverage reporting was also fixed for class coverage. The summary no longer reports
0.00%classes when Clover omits aggregatecoveredclasses; it derives class coverage from file-level metrics instead.Current Coverage
Latest successful backend CI run:
29675093569Latest Clover check reports no uncovered backend statements.
Coverage Added
Setting/Auth/DBfacade adapters, and the isolated Anthropic test-error HTTP boundary. Their calling behavior is covered through injectable/overridable helpers.Validation
composer lintphp -lon touched backend source/test filesgit diff --checkgit diff --cached --checkNotes
Local
composer test:unitremains blocked in this shell because Pest dependencies are not installed locally (Unable to find Pest. Run composer install first.). CI installs dependencies and is the authoritative backend test/coverage signal for this PR.