Skip to content

Daily Test Coverage Improver - Fix Vitest Coverage Command#8022

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
test/fix-coverage-steps-vitest-command-1d004173e3b537bd
Draft

Daily Test Coverage Improver - Fix Vitest Coverage Command#8022
github-actions[bot] wants to merge 1 commit into
mainfrom
test/fix-coverage-steps-vitest-command-1d004173e3b537bd

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Issue

The coverage-steps action.yml was using an incorrect Vitest flag --coverageDirectory which is not supported by Vitest 4.x. This caused the coverage tests to fail during execution.

Fix

Removed the --coverageDirectory=coverage flag from both React and backend.ai-ui test commands. The coverage directory configuration is already properly set in the vitest.config.ts files for both projects:

coverage: {
  provider: 'v8',
  reporter: ['text', 'json', 'json-summary', 'html'],
  reportsDirectory: 'coverage',  // ← Already configured
  // ...
}

Changes

  • Removed --coverageDirectory=coverage from React tests command
  • Removed --coverageDirectory=coverage from backend.ai-ui tests command

Testing

The fix has been committed and ready for testing in CI.

What Happens Next

Once this PR is merged, the coverage steps should execute successfully and Phase 3 of the Daily Test Coverage Improver workflow will be able to proceed with actual test coverage improvements.

AI generated by Daily Test Coverage Improver

The --coverageDirectory flag is not supported in Vitest. Coverage
configuration is already set in vitest.config.ts files, which specify
reportsDirectory: 'coverage' for both projects.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@cla-assistant

cla-assistant Bot commented Jun 23, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

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.

1 participant