feat(atomic): wire VitestA11yReporter into storybook vitest project#7126
Closed
y-lakhdar wants to merge 4 commits intofeat/a11y-scriptsfrom
Closed
feat(atomic): wire VitestA11yReporter into storybook vitest project#7126y-lakhdar wants to merge 4 commits intofeat/a11y-scriptsfrom
y-lakhdar wants to merge 4 commits intofeat/a11y-scriptsfrom
Conversation
Add @coveo/atomic-a11y as a dev dependency and configure VitestA11yReporter as a reporter in the storybook vitest project. When test:storybook runs, the reporter captures axe-core a11y results from each story test and writes an aggregated JSON report to packages/atomic-a11y/reports/a11y-report.json.
y-lakhdar
temporarily deployed
to
pr-workflows
GitHub Actions
Inactive
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
coveo-code-areas-pr-checks
bot
added
area:atomic
area:node-dependencies
team:dxui
labels
y-lakhdar
had a problem deploying
to
Prerelease (CDN)
GitHub Actions
Failure
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c2ffd50a50
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "@coveo/atomic-legacy": "workspace:*" | ||
| }, | ||
| "devDependencies": { | ||
| "@coveo/atomic-a11y": "workspace:*", |
There was a problem hiding this comment.
Adding @coveo/atomic-a11y in packages/atomic/package.json without a matching pnpm-lock.yaml update will break installs in CI: the setup action runs pnpm install --frozen-lockfile (.github/actions/setup/action.yml:41), and the packages/atomic importer in the current lockfile still has no @coveo/atomic-a11y entry, so pnpm will treat the lockfile as stale and fail before tests execute.
Useful? React with 👍 / 👎.
y-lakhdar
temporarily deployed
to
pr-workflows
GitHub Actions
Inactive
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
Prerelease (CDN)
GitHub Actions
Failure
This was referenced Feb 16, 2026
y-lakhdar
temporarily deployed
to
pr-workflows
GitHub Actions
Inactive
y-lakhdar
temporarily deployed
to
pr-workflows
GitHub Actions
Inactive
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
Prerelease (CDN)
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
Prerelease (CDN)
GitHub Actions
Failure
y-lakhdar
temporarily deployed
to
pr-workflows
GitHub Actions
Inactive
y-lakhdar
temporarily deployed
to
pr-workflows
GitHub Actions
Inactive
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
Prerelease (CDN)
GitHub Actions
Failure
y-lakhdar
had a problem deploying
to
Prerelease (CDN)
GitHub Actions
Failure
Contributor
Author
|
Closing — the wiring changes ( The PR chain is now 6 PRs instead of 7. PR #7117 ( |
y-lakhdar
had a problem deploying
to
PR Artifacts
GitHub Actions
Failure
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
1 participant
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.
Context
Bridges the reporter implementation (PR #7123) and the CI integration (PR #7117) by wiring
VitestA11yReporterinto thepackages/atomicstorybook vitest project.Try it
View the json report in
packages/atomic-a11y/reports/a11y-report.jsonPR Chain (6 of 7)
feat/a11y-package-scaffoldfeat/a11y-shared-foundationfeat/a11y-reporterfeat/a11y-openacrfeat/a11y-scriptsfeat/a11y-reporter-wiringfeat/a11y-ci-integration