Repository navigation
[CI/CD]: Unit tests are broken and not executed in CI checks workflow #8176
Description
Activity
- added a commit that references this issue
on Oct 5, 2026 Hi @suryaff733 sir , could you please review the current approach for #8176 #8181 and let me know if this direction is acceptable?
I’ve migrated the testing setup from Enzyme toward React Testing Library, added the Jest/RTL configuration and mocks, updated the test script and CI, and preserved the meaningful
source_urlbehavioral tests.One point I’d especially like your guidance on: several of the existing component tests currently require additional Gatsby/router/library mocks or component-specific props/data to run successfully. Would you prefer that I:
- continue fixing and migrating all of those tests in this PR, or
- keep this PR focused on establishing the React 18-compatible testing infrastructure and migrate the remaining failing tests in follow-up PRs?
I’m happy to follow whichever approach is preferred. Thanks!
- added a commit that references this issue
on Oct 5, 2026 Hi @Rajkaran-122 , appreciate the enthusiasm and the work on #8181! 🙌
Just a heads-up: per CONTRIBUTING.md → Working on an Issue, the convention is to first comment asking the maintainers to assign the issue to you, and only start work and open a PR once it's assigned.
Without that, the PR risks going unreviewed, getting marked stale, and being closed without merge, since the guidelines note that work on unassigned issues "may go unaccepted".
Could you request assignment here and wait for their go-ahead before continuing? Thanks!
Hi @Rajkaran-122 , appreciate the enthusiasm and the work on #8181! 🙌
Just a heads-up: per CONTRIBUTING.md → Working on an Issue, the convention is to first comment asking the maintainers to assign the issue to you, and only start work and open a PR once it's assigned.
Without that, the PR risks going unreviewed, getting marked stale, and being closed without merge, since the guidelines note that work on unassigned issues "may go unaccepted".
Could you request assignment here and wait for their go-ahead before continuing? Thanks!
Ok
@suryaff733 Could you please assign it to me?
Sorry for the delayed response, @Rajkaran-122! And thanks for your interest and patience.
Please join our Slack here: Meshery Slack
Once you join, please introduce yourself in the channel and let us know here. I’ll coordinate with the maintainers and get the issue assigned to you. Thanks again!
Reacted by RajkaranSorry for the delayed response, @Rajkaran-122! And thanks for your interest and patience.
Please join our Slack here: Meshery Slack
Once you join, please introduce yourself in the channel and let us know here. I’ll coordinate with the maintainers and get the issue assigned to you. Thanks again!
I joined the channel
Hey @Rajkaran-122, glad you joined! 🙌
Since I don’t have permission to assign the issue directly, please share the issue link and your PR link in <https://mesheryio.slack.com/archives/CFGG6U10|this Meshery channel> and request a maintainer to assign it to you.
Once it’s assigned, you can continue with the work. I’ll review your PR as well. Thanks for your patience and interest in contributing!
Current Behavior
All 46 unit test files across the repository (
src/**/*.test.js) andsrc/setupTests.jsare broken and cannot execute:src/setupTests.jsand 45 test suites importenzymeandenzyme-adapter-react-16. Neither package is installed inpackage.json, and Enzyme is incompatible with the project's React 18 (MODULE_NOT_FOUNDon execution).src/sections/Community/Members-grid/index.test.jsis a 0-byte empty file.package.jsonlacks a"test"script, and.github/workflows/checks.ymlnever executes tests during PR checks, allowing broken test suites to persist unnoticed.Desired Situation
enzymeto React Testing Library (@testing-library/react) with React 18 support and a modern test runner (e.g., Jest / Vitest).src/setupTests.jsto configure@testing-library/jest-dom."test"script (e.g.,"test": "jest") topackage.json.npm teststep to.github/workflows/checks.ymlso unit tests are automatically verified on every Pull Request.