-
Notifications
You must be signed in to change notification settings - Fork 0
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
PADV-1658 test: Shared Components Test Suite #20
Conversation
c8e476c
to
161a544
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.
In general I think the 98% of the comments are not necessary and that's because the test is descriptive itself maybe in some cases like the gauges make sense.
Sure!, but given so many tests of that tool that I don't know well, for me they were very useful. I Will erased all those comments |
6e7af87
to
c8548d9
Compare
c8548d9
to
29cf066
Compare
Tickets
Description
This PR focuses on enhancing and completing the test coverage for shared components utilized across the application. The aim is to ensure that all reusable components are thoroughly tested to guarantee their reliability and robustness.
Includes:
Shared Components:
AlertMessage: Verifies rendering, message display, and error handling logic.
LabDetailsCard: Tests for correct lab detail representation, edge cases, and data handling.
LabDetailsChartCard: Ensures that chart data is correctly processed and displayed.
Table: Covers table rendering, data population, empty states, and interactions like sorting and pagination.
TableFilter: Validates filtering logic, form handling, and integration with the table component.
DashboardLaunchButton: Ensures button visibility, click events, error handling, and integration with the dashboard launch logic.
JsonViewer: Verifies JSON editor initialization, configuration, and cleanup behavior.
Changes Made
This PR aims to achieve full coverage for all shared components, ensuring they function correctly in all intended use cases. Expected coverage for all shared components is at least 87%
How To Test
npm i
in your MFE folder.npm test -- --verbose
Verify that all tests pass and that coverage reports indicate the coverage for the targeted files.
Component Tests
Shared