Skip to content

feat: add CI workflow for tests with Allure v3 reporting - #72

Merged
Adammatthiesen merged 7 commits into
mainfrom
adam/repo-testing
Feb 21, 2026
Merged

Adammatthiesen merged 7 commits into
mainfrom
adam/repo-testing

Conversation

@Adammatthiesen

Copy link
Copy Markdown
Member

This pull request introduces a comprehensive overhaul of the testing workflow, focusing on integrating Allure reporting and streamlining test configuration. The main changes include replacing custom test scripts with Allure-based commands, adding Allure configuration files, updating dependencies, and refactoring Vitest configurations for improved consistency and maintainability.

Testing workflow and reporting integration:

  • Added .github/workflows/ci-testing.yml to run tests with Allure reporting, including setup for Apollo Git Bot, dependency installation, test execution, and Allure report generation.
  • Introduced allurerc.mjs for custom Allure report configuration, specifying output paths, history, and plugins for enhanced reporting features.

Test scripts and dependency updates:

  • Updated package.json to use vitest for testing, added Allure-related scripts (ci:test, allure:view), and included Allure and Vitest dependencies for reporting and test execution. [1] [2]

Vitest configuration refactoring:

  • Added vitest.config.ts for centralized test project management, Allure reporter setup, coverage configuration, and project grouping, replacing scattered test settings.
  • Created vitest.shared.ts to provide shared Vitest project configuration, ensuring consistent setup (Allure initialization, Node environment) across all test projects.
  • Refactored packages/css-js-gen/vitest.config.ts to merge shared config and define project-specific settings, improving maintainability and consistency.

Workflow cleanup:

  • Removed the css-js-gen-tests job from .github/workflows/ci-pull-request.yml as part of consolidating test execution under the new Allure-based workflow.

- Created a GitHub Actions workflow to run tests on pull requests to the main branch.
- Integrated Allure reporting for test results.
- Added configuration for Allure report generation in allurerc.mjs.
- Set up Vitest configuration to manage test projects and reporting.
- Introduced shared Vitest configuration for consistent test setup across projects.
@changeset-bot

changeset-bot Bot commented Feb 21, 2026 •

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 2a3a687

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
css-js-gen Patch
expressive-code-twoslash Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@htg-1-studiocms-cloud

htg-1-studiocms-cloud Bot commented Feb 21, 2026 •

Copy link
Copy Markdown

Dokploy Preview Deployment

Name Status Preview Updated (UTC)
Expressive-Code-Twoslash Docs ✅ Done Preview URL 2026-02-21T01:39:14.698Z

@apollo-git-bot

apollo-git-bot Bot commented Feb 21, 2026 •

Copy link
Copy Markdown
Contributor

Allure Report Summary

Name Duration Stats New Flaky Retry Report
css-js-gen Tests 11ms Passed tests 37 37 0 0

@pkg-pr-new

pkg-pr-new Bot commented Feb 21, 2026 •

Copy link
Copy Markdown
npm i https://pkg.pr.new/withstudiocms/expressive-code-twoslash/css-js-gen@72
npm i https://pkg.pr.new/withstudiocms/expressive-code-twoslash@72

commit: 2a3a687

@Adammatthiesen
Adammatthiesen marked this pull request as ready for review February 21, 2026 01:46
@Adammatthiesen
Adammatthiesen requested a review from a team as a code owner February 21, 2026 01:46
@Adammatthiesen Adammatthiesen changed the title [WIP] feat: add CI workflow for tests with Allure v3 reporting feat: add CI workflow for tests with Allure v3 reporting Feb 21, 2026
@Adammatthiesen
Adammatthiesen merged commit 21c4812 into main Feb 21, 2026
12 checks passed
@Adammatthiesen
Adammatthiesen deleted the adam/repo-testing branch February 21, 2026 02:01
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.

2 participants