ATLAS-5294: ATLAS UI: Shared component library tests#634
Open
pawarprasad123 wants to merge 1 commit into
Open
Conversation
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
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.
What changes were proposed in this pull request?
Add unit tests for shared React components.
This PR tests reusable UI (forms, tables, query builder, search, show-more, etc.). These components are imported by many views; tests here prevent regressions across the whole app.
This PR covers primary navigation and high-traffic surfaces: home/overview charts, app chrome (header/layout), lineage entry, sidebar trees, saved filters, search results, and server/entity statistics views.
What changes do
Verify rendering, user events, accessibility-oriented queries, and edge cases (empty data, disabled states) in isolation with mocks for Redux/router when needed.
Reduce duplicate debugging: a bug in
TableLayoutorQuickSearchwould otherwise appear as failures in many unrelated feature tests.DashboardOverviewtests: Charts and cards (e.g. entity types, Kafka summary, latest entities, message consumption) with Recharts/MUI mocked where needed.Layout/Lineagetests: Shell behavior users see on almost every route.SideBar/Importtests: Tree navigation and glossary import dropzone flows.SearchResult/SaveFilterstests: Discovery and saved-query UX.Statisticstests: Metrics screens and graph tooltips.Why these files are used
How was this patch tested?
Manual test