Skip to content

Daily Test Coverage Improver - Fix coverage steps configuration#7924

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
test/fix-coverage-steps-action-8f6817be03111b5d
Draft

Daily Test Coverage Improver - Fix coverage steps configuration#7924
github-actions[bot] wants to merge 1 commit into
mainfrom
test/fix-coverage-steps-action-8f6817be03111b5d

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Summary

Fixed invalid vitest CLI options in the coverage steps action that were causing test runs to fail.

Problem

The action.yml was using --coverageDirectory option which is not valid in vitest 4.x:

CACError: Unknown option `--coverageDirectory`

Solution

Removed the --coverageDirectory option from both React and backend.ai-ui test commands. The coverage output directory is already properly configured in vitest.config.ts files via the reportsDirectory: 'coverage' setting.

Changes

  • Removed --coverageDirectory=coverage from React test command
  • Removed --coverageDirectory=coverage from backend.ai-ui test command
  • Coverage reports will still be generated in the coverage/ directories as configured

Verification

The fix aligns with the vitest configuration:

  • React: react/vitest.config.ts sets reportsDirectory: 'coverage'
  • backend.ai-ui: Uses same vitest configuration pattern

What Happens Next

Once this PR is merged:

  • The coverage steps will successfully run tests and generate coverage reports
  • Phase 3 of the Daily Test Coverage Improver workflow can proceed
  • Systematic test coverage improvements can begin

AI generated by Daily Test Coverage Improver

…ands

The --coverageDirectory option is not valid in vitest 4.x. Coverage
output directory is configured via vitest.config.ts with the
reportsDirectory setting, which is already set to 'coverage' for both
React and backend.ai-ui projects.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants