pawarprasad123 opened a new pull request, #635: URL: https://github.com/apache/atlas/pull/635
## What changes were proposed in this pull request? Add tests for detail page, entity tabs, and related sublayouts Add tests for admin flows, glossary/ classification/ BM, integration suites This PR focuses on **entity (and related) detail UX**: attributes, classifications, audits, lineage inside the detail context, schema, relationships, glossary term panels, relationship detail layout, etc. This PR adds **feature tests** for **administrator** screens (audits, enums, type tree, etc.), **glossary** and **classification** flows, **business metadata** forms, plus **cross-cutting** tests at `src/__tests__` (router, `Main`, error boundary, license header, optional dependency governance). **What changes do** - Tests mount **realistic page fragments** with router params, mocked API, and Redux slices to assert **tab behavior**, **tables**, **modals**, and **error/loading** states. - Catches regressions in **large** components (e.g. lineage, schema) that are hard to cover only via shallow component tests. - **`views/Administrator/**/__tests__`**: Admin-only workflows (audit tables, filters, import/export audits, layout). - **`views/BusinessMetadata/__tests__`**, **`Classification/__tests__`**, **`Glossary/__tests__`**: Metadata stewardship CRUD and assignment flows. - **`src/__tests__/**`**: Broader integration smoke tests and repo policy checks (`apache-license-header`), optional **dependency governance** (`RUN_DEPENDENCY_GOVERNANCE=1`) with **`fixtures/dependabot-alerts.sample.json`**. **Why these files are used** - Detail page is where **most governance actions** surface (tags, terms, BM attributes); automated tests reduce risk for **data correctness** and **workflow** regressions. - Admin/glossary/classification areas have **complex forms** and **permissions-sensitive** behavior; integration tests catch **route + store + API** mismatches. ## How was this patch tested? Manual test -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
