-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unit tests for Namespace filtering in resources #7465
Add unit tests for Namespace filtering in resources #7465
Conversation
…ata-testid attributes for testing purposes and ocmments for readability
07d9545
to
8e276c3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the tests look great. I just have a few comments on spy usage, todos, and tsc warnings 🙂
20657f7
to
547c846
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@catherineluse I have created a new issue here: #7495 |
@catherineluse Taking a look to the code, I see nothing which may cause issues, rather the other way around, to prevent access function when undefined. In the same way I don't see any other commit either since a while. |
Summary
Fixes #7391
These tests are aimed to ensure the functionalities of the namespace filter an part of the Workload fetching data capabilities.
Occurred changes and/or fixed issues
NamespaceFilter
component in case of missing props or data, e.g.currentProduct
data-testid
attributes for selecting component.Technical notes summary
Areas or cases that should be tested
Areas which could experience regressions
Screenshot/Video