Add unit test infrastructure and inline snapshot tests#245
Merged
keithchong merged 2 commits intoJun 17, 2026
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds Jest configuration, dev tooling, test scripts, a GitHub Actions workflow for coverage reporting, nine Jest mock modules for external dependencies, and a comprehensive suite of snapshot and unit tests covering UI components, utilities, services, pod/container logic, graph helpers, and rollout state analysis. ChangesJest Testing Infrastructure & Test Coverage
🎯 3 (Moderate) | ⏱️ ~25 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (2)
.github/workflows/unit-tests.yml (1)
13-13: 💤 Low valueConsider pinning actions to commit SHAs and setting persist-credentials: false.
For enhanced supply chain security:
- Pin actions to specific commit SHAs instead of version tags (e.g.,
actions/checkout@<commit-sha>instead of@v4)- Add
persist-credentials: falseto the checkout step to prevent credentials from persisting in.git/configThese are defense-in-depth measures against potential action tag manipulation and credential leakage through artifacts.
🔒 Example of hardened checkout step
- - uses: actions/checkout@v4 + - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1 + with: + persist-credentials: false🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/unit-tests.yml at line 13, Replace the loose actions/checkout@v4 reference with a pinned commit SHA (use the specific commit hash for actions/checkout you want) and add the checkout input persist-credentials: false; specifically update the checkout step that currently uses "actions/checkout@v4" to use "actions/checkout@<commit-sha>" and include the key persist-credentials: false so credentials are not persisted to .git/config.Source: Linters/SAST tools
__mocks__/patternfly-react-tokens.ts (1)
1-5: 💤 Low valueSimplify redundant CommonJS exports.
Lines 4–5 export the same token object via
module.exportsafter the ES6 default export (line 3). Jest handles both import styles correctly with just the ES6 export; the CommonJS assignments are redundant and can be removed.Optional: Simplify to ES6-only export
const token = { name: 'mock-token', value: '`#000000`', var: 'var(--mock-token)' }; export default token; -module.exports = token; -module.exports.default = token;🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@__mocks__/patternfly-react-tokens.ts` around lines 1 - 5, The mock exports duplicate the ES module default by also assigning module.exports and module.exports.default; remove the redundant CommonJS lines so only the ES6 export remains (keep the const token = { ... } and the export default token), ensuring the symbol token and the export default token line are preserved and delete the module.exports = token and module.exports.default = token assignments.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@__mocks__/patternfly-react-tokens.ts`:
- Around line 1-5: The mock exports duplicate the ES module default by also
assigning module.exports and module.exports.default; remove the redundant
CommonJS lines so only the ES6 export remains (keep the const token = { ... }
and the export default token), ensuring the symbol token and the export default
token line are preserved and delete the module.exports = token and
module.exports.default = token assignments.
In @.github/workflows/unit-tests.yml:
- Line 13: Replace the loose actions/checkout@v4 reference with a pinned commit
SHA (use the specific commit hash for actions/checkout you want) and add the
checkout input persist-credentials: false; specifically update the checkout step
that currently uses "actions/checkout@v4" to use "actions/checkout@<commit-sha>"
and include the key persist-credentials: false so credentials are not persisted
to .git/config.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: 5e16eca8-e1c2-466a-a862-2c820c6e8e25
⛔ Files ignored due to path filters (1)
yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (37)
.github/workflows/unit-tests.yml.gitignore__mocks__/dynamic-plugin-sdk.tsx__mocks__/json-schema.ts__mocks__/patternfly-react-core.tsx__mocks__/patternfly-react-icons.tsx__mocks__/patternfly-react-table.tsx__mocks__/patternfly-react-tokens.ts__mocks__/patternfly-react-topology.ts__mocks__/react-i18next.ts__mocks__/style-mock.tsjest.config.tspackage.jsonsrc/gitops/Revision/Revision.test.tsxsrc/gitops/Statuses/HealthStatus.test.tsxsrc/gitops/Statuses/OperationState.test.tsxsrc/gitops/Statuses/SyncStatus.test.tsxsrc/gitops/components/graph/utils.test.tssrc/gitops/components/rollout/revisions/ReplicaSetInfo.test.tssrc/gitops/components/rollout/utils/rollout-utils.test.tssrc/gitops/components/shared/MetadataLabels/MetadataLabels.test.tsxsrc/gitops/components/shared/pod-utils.test.tssrc/gitops/services/ArgoCD.test.tssrc/gitops/topology/actions/creators.test.tssrc/gitops/utils/components/ActionDropDown/ActionDropDown.test.tsxsrc/gitops/utils/components/ActionDropDownItem/ActionDropDownItem.test.tsxsrc/gitops/utils/components/ExternalLink/ExternalLink.test.tsxsrc/gitops/utils/components/OwnerReferences/OwnerReferences.test.tsxsrc/gitops/utils/components/toggles/toggles.test.tsxsrc/gitops/utils/gitops.test.tssrc/gitops/utils/project-utils.test.tssrc/gitops/utils/stringHelpers.test.tssrc/gitops/utils/urls.test.tssrc/gitops/utils/utils.test.tssrc/plugin/import/badges/TechPreviewBadge.test.tsxsrc/plugin/status/icons.test.tsxsrc/plugin/utils/flags/enableGitOpsDynamicFlag.test.ts
Set up Jest with ts-jest, jsdom, and module mocks for PatternFly, OpenShift Console SDK, and react-i18next. All tests use toMatchInlineSnapshot() for zero-friction maintenance (jest -u). 24 test suites, 144 tests, 203 inline snapshots covering utility functions, service layer, and React components. Adds a GitHub Actions workflow to run tests and upload coverage to Codecov with the unit-tests flag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Adam Saleh <adam@asaleh.net>
AdamSaleh
force-pushed
the
add-unit-test-coverage
branch
from
0e7f2a3 to
fd94b45
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
src/gitops/utils/components/ActionDropDown/ActionDropDown.test.tsx (1)
5-39: ⚡ Quick winSnapshot scope is too brittle and misses the dropdown’s core behavior contract.
These tests currently lock mock serialization details (e.g.,
popperProps="[object Object]") and only validate the closed render path, but they don’t verify the first-openonLazyClickcontract fromActionDropDown.tsx. Prefer semantic assertions for stable DOM signals and add one behavior-focused test foronLazyClickfiring on first open.As per coding guidelines, “Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/gitops/utils/components/ActionDropDown/ActionDropDown.test.tsx` around lines 5 - 39, The tests in ActionDropDown.test.tsx use fragile full HTML snapshots (including popperProps) and miss the behavioral contract for the first-open lazy-loading; update the tests to use semantic assertions instead of inline snapshots for ActionsDropdown (check presence/attributes of the toggle button and absence/presence of menu items) and add a behavior test that mounts ActionsDropdown with a jest.fn() onLazyClick, simulates a user click on the toggle (using fireEvent or userEvent) to open the dropdown, and asserts that the onLazyClick handler (referenced as onLazyClick in ActionDropDown/ActionsDropdown) is called exactly once on the first open; remove or avoid asserting serialized popperProps and focus on stable DOM signals like data-testid="dropdown" and visible menu items.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/unit-tests.yml:
- Line 13: Replace mutable action tags with pinned commit SHAs for every `uses:`
entry that currently references a floating tag (e.g., `actions/checkout@v4`,
`actions/setup-node@v5`, and the other `uses:` entry at line 24) by looking up
the corresponding official action repository and substituting the full immutable
commit SHA (e.g., `actions/checkout@<full-sha>`). Update each `uses:` reference
in the workflow to the exact commit SHA while preserving the existing inputs and
behavior so CI execution is stable and supply-chain hardened.
- Line 13: Update the actions/checkout step (actions/checkout@v4) to disable
credential persistence by adding persist-credentials: false and restrict the
workflow job permissions to the minimal scopes needed for npm/yarn (e.g., remove
write or repo-level tokens and grant only contents: read and packages: read if
necessary) so that running dependency-managed scripts like yarn install and yarn
test:coverage cannot persist or exfiltrate the checkout token.
---
Nitpick comments:
In `@src/gitops/utils/components/ActionDropDown/ActionDropDown.test.tsx`:
- Around line 5-39: The tests in ActionDropDown.test.tsx use fragile full HTML
snapshots (including popperProps) and miss the behavioral contract for the
first-open lazy-loading; update the tests to use semantic assertions instead of
inline snapshots for ActionsDropdown (check presence/attributes of the toggle
button and absence/presence of menu items) and add a behavior test that mounts
ActionsDropdown with a jest.fn() onLazyClick, simulates a user click on the
toggle (using fireEvent or userEvent) to open the dropdown, and asserts that the
onLazyClick handler (referenced as onLazyClick in
ActionDropDown/ActionsDropdown) is called exactly once on the first open; remove
or avoid asserting serialized popperProps and focus on stable DOM signals like
data-testid="dropdown" and visible menu items.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: d91bc223-224d-47b3-b3c5-b16349c2fe97
⛔ Files ignored due to path filters (1)
yarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (37)
.github/workflows/unit-tests.yml.gitignore__mocks__/dynamic-plugin-sdk.tsx__mocks__/json-schema.ts__mocks__/patternfly-react-core.tsx__mocks__/patternfly-react-icons.tsx__mocks__/patternfly-react-table.tsx__mocks__/patternfly-react-tokens.ts__mocks__/patternfly-react-topology.ts__mocks__/react-i18next.ts__mocks__/style-mock.tsjest.config.tspackage.jsonsrc/gitops/Revision/Revision.test.tsxsrc/gitops/Statuses/HealthStatus.test.tsxsrc/gitops/Statuses/OperationState.test.tsxsrc/gitops/Statuses/SyncStatus.test.tsxsrc/gitops/components/graph/utils.test.tssrc/gitops/components/rollout/revisions/ReplicaSetInfo.test.tssrc/gitops/components/rollout/utils/rollout-utils.test.tssrc/gitops/components/shared/MetadataLabels/MetadataLabels.test.tsxsrc/gitops/components/shared/pod-utils.test.tssrc/gitops/services/ArgoCD.test.tssrc/gitops/topology/actions/creators.test.tssrc/gitops/utils/components/ActionDropDown/ActionDropDown.test.tsxsrc/gitops/utils/components/ActionDropDownItem/ActionDropDownItem.test.tsxsrc/gitops/utils/components/ExternalLink/ExternalLink.test.tsxsrc/gitops/utils/components/OwnerReferences/OwnerReferences.test.tsxsrc/gitops/utils/components/toggles/toggles.test.tsxsrc/gitops/utils/gitops.test.tssrc/gitops/utils/project-utils.test.tssrc/gitops/utils/stringHelpers.test.tssrc/gitops/utils/urls.test.tssrc/gitops/utils/utils.test.tssrc/plugin/import/badges/TechPreviewBadge.test.tsxsrc/plugin/status/icons.test.tsxsrc/plugin/utils/flags/enableGitOpsDynamicFlag.test.ts
✅ Files skipped from review due to trivial changes (3)
- .gitignore
- mocks/patternfly-react-core.tsx
- mocks/patternfly-react-table.tsx
🚧 Files skipped from review as they are similar to previous changes (30)
- mocks/style-mock.ts
- src/plugin/utils/flags/enableGitOpsDynamicFlag.test.ts
- src/gitops/utils/components/OwnerReferences/OwnerReferences.test.tsx
- src/gitops/topology/actions/creators.test.ts
- src/gitops/utils/stringHelpers.test.ts
- src/gitops/components/shared/pod-utils.test.ts
- src/gitops/components/rollout/utils/rollout-utils.test.ts
- mocks/patternfly-react-topology.ts
- src/gitops/utils/urls.test.ts
- src/gitops/utils/components/toggles/toggles.test.tsx
- src/gitops/components/shared/MetadataLabels/MetadataLabels.test.tsx
- mocks/react-i18next.ts
- mocks/json-schema.ts
- src/gitops/components/rollout/revisions/ReplicaSetInfo.test.ts
- src/gitops/Statuses/OperationState.test.tsx
- src/plugin/status/icons.test.tsx
- src/gitops/Revision/Revision.test.tsx
- mocks/patternfly-react-tokens.ts
- src/gitops/utils/project-utils.test.ts
- jest.config.ts
- src/gitops/components/graph/utils.test.ts
- src/gitops/utils/gitops.test.ts
- src/gitops/Statuses/SyncStatus.test.tsx
- src/gitops/utils/components/ExternalLink/ExternalLink.test.tsx
- src/plugin/import/badges/TechPreviewBadge.test.tsx
- mocks/patternfly-react-icons.tsx
- src/gitops/utils/utils.test.ts
- src/gitops/services/ArgoCD.test.ts
- package.json
- mocks/dynamic-plugin-sdk.tsx
| test: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 |
There was a problem hiding this comment.
Pin all GitHub Actions to immutable commit SHAs.
Line 13, Line 15, and Line 24 use mutable tags (@v4, @v5). That leaves CI behavior vulnerable to upstream tag movement or supply-chain compromise. Pin each uses: reference to a full commit SHA.
Suggested hardening patch
- - uses: actions/checkout@v4
+ - uses: actions/checkout@<full-commit-sha>
- - uses: actions/setup-node@v4
+ - uses: actions/setup-node@<full-commit-sha>
- - uses: codecov/codecov-action@v5
+ - uses: codecov/codecov-action@<full-commit-sha>Also applies to: 15-15, 24-24
🧰 Tools
🪛 zizmor (1.25.2)
[warning] 13-13: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
[error] 13-13: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)
(unpinned-uses)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/unit-tests.yml at line 13, Replace mutable action tags
with pinned commit SHAs for every `uses:` entry that currently references a
floating tag (e.g., `actions/checkout@v4`, `actions/setup-node@v5`, and the
other `uses:` entry at line 24) by looking up the corresponding official action
repository and substituting the full immutable commit SHA (e.g.,
`actions/checkout@<full-sha>`). Update each `uses:` reference in the workflow to
the exact commit SHA while preserving the existing inputs and behavior so CI
execution is stable and supply-chain hardened.
Source: Linters/SAST tools
Disable checkout credential persistence before running dependency-controlled scripts.
On Line 13, actions/checkout defaults to persisting the token in local git config. Since Line 20/22 execute package-managed scripts (yarn install, yarn test:coverage), this unnecessarily enlarges token exfiltration risk. Set persist-credentials: false and scope job permissions minimally.
Suggested hardening patch
+permissions:
+ contents: read
+
jobs:
test:
runs-on: ubuntu-latest
steps:
- - uses: actions/checkout@v4
+ - uses: actions/checkout@<full-commit-sha>
+ with:
+ persist-credentials: false🧰 Tools
🪛 zizmor (1.25.2)
[warning] 13-13: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false
(artipacked)
[error] 13-13: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)
(unpinned-uses)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/unit-tests.yml at line 13, Update the actions/checkout
step (actions/checkout@v4) to disable credential persistence by adding
persist-credentials: false and restrict the workflow job permissions to the
minimal scopes needed for npm/yarn (e.g., remove write or repo-level tokens and
grant only contents: read and packages: read if necessary) so that running
dependency-managed scripts like yarn install and yarn test:coverage cannot
persist or exfiltrate the checkout token.
Source: Linters/SAST tools
keithchong
reviewed
Jun 15, 2026
| getResourceNodeSyncStatus, | ||
| } from './utils'; | ||
|
|
||
| describe('kindToAbbr', () => { |
Collaborator
There was a problem hiding this comment.
This looks like a good test of this particular function
| }); | ||
| }); | ||
|
|
||
| describe('getTopologyNodeStatus', () => { |
Collaborator
There was a problem hiding this comment.
This is a good test possibly to prevent changes in what it returns in the future. eg. changing the return value inadvertantly will signify a 'breaking' change from what was the original expected value
| }); | ||
| }); | ||
|
|
||
| describe('createSpacerNode', () => { |
| @@ -0,0 +1,23 @@ | |||
| import { isDeploying } from './rollout-utils'; | |||
Collaborator
There was a problem hiding this comment.
Seems lik a good unit test for isDeploying
| @@ -0,0 +1,73 @@ | |||
| import { renderToStaticMarkup } from 'react-dom/server'; | |||
| import Revision from './Revision'; | |||
|
|
|||
Collaborator
There was a problem hiding this comment.
The test is missing the return of None, but this seems like a good start for provide a unit test.
I like the test for sha256 versusn non-sha256 revisions.
keithchong
reviewed
Jun 15, 2026
| @@ -0,0 +1,28 @@ | |||
| name: Unit Tests | |||
|
|
|||
Collaborator
There was a problem hiding this comment.
Thanks for doing this Adam. Similar to Argo CD, it uses jest as well.
I think we should keep what you have.
Collaborator
|
LGTM. I think this is a good foundation to build on. Non-blocking but would help to have README testing section. |
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Adam Saleh <adam@asaleh.net>
Member
Author
|
@aali309 added that readme :) |
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
4 participants
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.
Summary
unit-testsflagAll tests use
toMatchInlineSnapshot()— expected values live in the source file and auto-update withjest -u. No external fixture files, no manual snapshot maintenance.What's tested
Mock infrastructure
9 mock files in
__mocks__/stub external dependencies for Jest:dynamic-plugin-sdk.tsx— OpenShift Console SDK types, icons, and K8s helperspatternfly-react-core.tsx— Button, Popover, Dropdown, Tooltip, Label, etc.patternfly-react-icons.tsx,patternfly-react-table.tsx,patternfly-react-topology.ts,patternfly-react-tokens.tsreact-i18next.ts,json-schema.ts,style-mock.tsNote: Adding a new PatternFly or SDK import to source code may require updating the corresponding mock file.
Why renderToStaticMarkup instead of @testing-library/react
The project uses React 17.0.2.
@testing-library/react@14+requires React 18'sreact-dom/client.renderToStaticMarkupworks with React 17 and produces deterministic HTML suitable for inline snapshots.Test plan
yarn test— 24 suites, 144 tests, 203 snapshots passyarn test:coverage— generates coverage reportjest -u— all snapshots auto-update🤖 Generated with Claude Code