Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-12T00:28:53.713Z
Learning: In talawa-admin PR #4565 continuation (PR #4664 planned), Phase 2A mock isolation strategy uses global vi.clearAllMocks() in afterEach (vitest.setup.ts) plus refactoring module-level vi.fn() into per-test beforeEach blocks across 6 parallelizable issues (2A.0 foundation, 2A.1-2A.4 directory-based fixes, 2A.5 validation). This approach addresses mock call history accumulation enabling maxConcurrency: 2 and 2.3-2.5x speedup. vi.restoreAllMocks() alternative considered for spy restoration during validation phase. Phase 2A (mocks) correctly separated from Phase 2B (DOM/Apollo).

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-11T11:51:09.236Z
Learning: In talawa-admin PR #4664 (continuation of PR #4565 sharding work), global mock cleanup was implemented via vi.clearAllMocks() in vitest.setup.ts afterEach, along with Apollo Client warning suppression (temporary, pending follow-up PR) and test suite refactoring to per-test StaticMockLink instances. This test isolation strategy addresses mock state leakage that forced maxConcurrency: 1 in PR #4565, enabling future parallel test execution improvements and 3-4x speedup potential.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:409-0
Timestamp: 2025-08-20T18:04:34.194Z
Learning: In PR #4094, the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modification for initial implementation, with plans to refactor for consistency later.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:0-0
Timestamp: 2025-08-20T18:04:52.324Z
Learning: In PR #4094, the user confirmed that the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications for initial implementation, with plans to refactor for consistency later.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:435-0
Timestamp: 2025-08-20T18:04:23.118Z
Learning: In the talawa-admin codebase, pagination logic for the admin orglist page in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications to maintain consistency between the two implementations.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/OrganizationTags/OrganizationTags.tsx:370-373
Timestamp: 2024-10-30T13:16:35.635Z
Learning: In `src/screens/OrganizationTags/OrganizationTags.tsx`, when mapping rows for the DataGrid, use `index + 1` as the `id` because the index number plus one is required.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:409-0
Timestamp: 2025-08-20T18:04:34.194Z
Learning: In PR #4094, the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modification for initial implementation, with plans to refactor for consistency later.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:0-0
Timestamp: 2025-08-20T18:04:52.324Z
Learning: In PR #4094, the user confirmed that the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications for initial implementation, with plans to refactor for consistency later.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/OrganizationTags/OrganizationTags.tsx:350-376
Timestamp: 2024-10-30T13:18:56.627Z
Learning: In the `src/screens/OrganizationTags/OrganizationTags.tsx` file, the `OrganizationTags` component uses chunk size with the `InfiniteScroll` component and an outer parent div for handling data loading and scrolling.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:251-274
Timestamp: 2024-10-28T06:33:09.726Z
Learning: In `TagActions.test.tsx`, negative test cases for tag operations can be deferred and added later if necessary, according to the team's plan.

Learnt from: bitbard3
Repo: PalisadoesFoundation/talawa-admin PR: 2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:155-162
Timestamp: 2024-12-03T05:52:37.888Z
Learning: In the `ChangeLanguageDropdown` component (`src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.tsx`), error handling has not been implemented. Therefore, test cases in `src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx` do not cover error scenarios related to error handling.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/AddPeopleToTag/AddPeopleToTag.test.tsx:177-241
Timestamp: 2024-11-02T07:48:36.443Z
Learning: In `src/components/AddPeopleToTag/AddPeopleToTag.test.tsx`, prefer keeping test cases separate and more readable, even if it involves some duplication, instead of extracting common logic into helper functions.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/Requests/Requests.spec.tsx:0-0
Timestamp: 2025-10-22T22:22:27.696Z
Learning: In talawa-admin tests using react-infinite-scroll-component (e.g., src/screens/Requests/Requests.spec.tsx), jsdom scroll is flaky. Prefer a resilient approach: try querying the container via document.querySelector('[data-testid="infinite-scroll-component"]') and fall back to window scroll if missing. Strengthen assertions by checking for page-2 items (e.g., "User9 Test") to ensure fetchMore actually ran instead of relying only on row counts.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2718
File: src/screens/UserPortal/Settings/Settings.spec.tsx:0-0
Timestamp: 2024-12-22T17:58:17.818Z
Learning: The matchMedia mock implementation in `Settings.spec.tsx` no longer includes the deprecated addListener and removeListener methods, opting solely for addEventListener and removeEventListener.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4077
File: package.json:189-213
Timestamp: 2025-08-17T07:39:34.255Z
Learning: The Talawa Admin codebase primarily uses .spec.tsx/.spec.ts naming convention for unit tests, with Cypress tests using .cy.ts pattern. However, there is at least one .test.tsx file in the codebase, so NYC exclude patterns should include both .spec and .test patterns.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: public/locales/zh/translation.json:0-0
Timestamp: 2025-03-19T17:42:16.729Z
Learning: The PR #3814 focuses specifically on implementing sign up, sign in, sign out, and useSession in better auth (frontend), and translation changes in the Chinese localization file were not part of the intentional changes made by the author.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3988
File: cypress/e2e/admin_spec/people.cy.ts:25-33
Timestamp: 2025-07-02T19:15:13.036Z
Learning: In the talawa-admin project, specifically in cypress/e2e/admin_spec/people.cy.ts, the user syedali237 intentionally designed the "add an existing member" and "delete a member" tests to work simultaneously with interdependencies, where the delete test relies on the add test having run first.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/screens/UserPortal/Organizations/Organizations.spec.tsx:19-19
Timestamp: 2025-01-26T12:32:45.867Z
Learning: In React test files, avoid using React hooks outside component scope (including in static objects like mock data). Instead, initialize hooks inside describe blocks or extract the needed functionality without using hooks.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.spec.tsx:403-421
Timestamp: 2025-04-20T06:45:57.175Z
Learning: In the talawa-admin project, the Advertisement component tests (3 files) use both ApolloProvider and MockedProvider together, though it's not a widespread pattern in the codebase. The maintainer has confirmed this approach is needed for these specific tests.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-17T22:18:09.680Z
Learning: Talawa Admin Phase 2A testing guideline: Allow vi.hoisted() + vi.mock() module-level mocks for shared dependencies; prefer afterEach(() => vi.clearAllMocks()) as default cleanup. Use afterEach(() => vi.restoreAllMocks()) only in suites that create vi.spyOn spies or patch real implementations. Avoid vi.resetAllMocks() globally. The generic “no module-level mocks” rule is updated to “no module-level vi.fn except vi.hoisted module mocks.”

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-12T00:28:53.713Z
Learning: In talawa-admin PR #4565 continuation (PR #4664 planned), Phase 2A mock isolation strategy uses global vi.clearAllMocks() in afterEach (vitest.setup.ts) plus refactoring module-level vi.fn() into per-test beforeEach blocks across 6 parallelizable issues (2A.0 foundation, 2A.1-2A.4 directory-based fixes, 2A.5 validation). This approach addresses mock call history accumulation enabling maxConcurrency: 2 and 2.3-2.5x speedup. vi.restoreAllMocks() alternative considered for spy restoration during validation phase. Phase 2A (mocks) correctly separated from Phase 2B (DOM/Apollo).

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/components/LeftDrawerOrg/LeftDrawerOrg.test.tsx:282-282
Timestamp: 2024-09-29T06:51:31.295Z
Learning: In the test 'Component should be rendered properly' within 'Testing LeftDrawerOrg component for SUPERADMIN', setting 'SuperAdmin' to false is intentional.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.spec.tsx:403-421
Timestamp: 2025-04-20T06:45:57.175Z
Learning: Using both ApolloProvider and MockedProvider together in tests is an established pattern in this codebase, even though it's technically redundant from Apollo Client's best practices perspective.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-11T11:51:09.236Z
Learning: In talawa-admin PR #4664 (continuation of PR #4565 sharding work), global mock cleanup was implemented via vi.clearAllMocks() in vitest.setup.ts afterEach, along with Apollo Client warning suppression (temporary, pending follow-up PR) and test suite refactoring to per-test StaticMockLink instances. This test isolation strategy addresses mock state leakage that forced maxConcurrency: 1 in PR #4565, enabling future parallel test execution improvements and 3-4x speedup potential.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/screens/OrganizationTags/OrganizationTags.test.tsx:184-0
Timestamp: 2024-11-02T07:18:39.563Z
Learning: In the `talawa-admin` project, it's acceptable for test cases in `src/screens/OrganizationTags/OrganizationTags.test.tsx` to test multiple behaviors within a single test function without needing to split them into smaller, focused tests.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx:1-28
Timestamp: 2024-10-30T12:01:40.366Z
Learning: In the `MockAddPeopleToTag` component in `src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx`, it's acceptable to implement only the necessary props from `InterfaceAddPeopleToTagProps` and omit others like `refetchAssignedMembersData`, `t`, and `tCommon` that are tested separately.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3712
File: src/components/EventCalender/Yearly/YearlyEventCalender.spec.tsx:113-127
Timestamp: 2025-02-20T13:35:01.218Z
Learning: In React component tests, when testing window resize event handling, it's acceptable to only verify that the event is properly triggered without assertions if the test's focus is specifically on event handling rather than responsive behavior. Testing the actual responsive rendering would be a separate test case.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/components/TagActions/TagNode.tsx:174-176
Timestamp: 2024-10-30T15:29:21.628Z
Learning: In `src/components/TagActions/TagNode.tsx`, the `hasMore` prop in `InfiniteScroll` is correctly implemented, handling undefined data safely with optional chaining and nullish coalescing, and the infinite scrolling functionality is thoroughly tested.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:123-131
Timestamp: 2024-10-28T06:38:43.765Z
Learning: In `TagActions.test.tsx`, `link2` is the error link used to simulate errors, so the existing test cases sufficiently cover error handling.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 2482
File: src/components/AddOn/support/components/Action/Action.spec.tsx:1-8
Timestamp: 2024-11-27T06:37:47.871Z
Learning: In the Talawa-Admin project, the `testing-library/jest-dom` package is imported globally in `vitest.setup.ts`, so individual test files do not need to import it separately.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTag.tsx:58-97
Timestamp: 2024-10-30T13:38:29.300Z
Learning: In the `ManageTag` component (`src/screens/ManageTag/ManageTag.tsx`), extracting modal state management to a custom hook may require additional state modifications for the `toggle` and `show` functions.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/utils/useSession.tsx:51-51
Timestamp: 2025-03-11T17:24:35.930Z
Learning: When implementing logout functionality with the new "better auth" system, both `localStorage.clear()` and `authClient.signOut()` are used together to ensure complete cleanup of both client-side storage and server-side sessions.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/utils/useSession.tsx:29-30
Timestamp: 2025-03-11T17:23:01.696Z
Learning: In the useSession.tsx file, there's a commented-out session access hook that should remain in the codebase as an implementation example, but it's commented out to avoid unnecessary data fetching when the session data isn't immediately needed.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3491
File: src/components/UserPortal/SecuredRouteForUser/SecuredRouteForUser.tsx:34-43
Timestamp: 2025-02-06T20:56:05.378Z
Learning: In SecuredRouteForUser component, token updates between role switches (e.g., user to superAdmin) are better handled using separate useEffect hooks - one for initial token setup (empty deps) and another for refetch on token changes, rather than combining them into a single effect.

Learnt from: PratapRathi
Repo: PalisadoesFoundation/talawa-admin PR: 3923
File: src/GraphQl/Queries/Queries.ts:62-73
Timestamp: 2025-04-09T05:00:49.395Z
Learning: The ORGANIZATION_LIST_BY_SEARCH query in src/GraphQl/Queries/Queries.ts relies on search filtering rather than pagination to manage result set size, with the team planning to add limits later if needed.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts:0-0
Timestamp: 2025-10-22T22:00:53.943Z
Learning: In src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts (and similar mock files), avoid duplicating identical Apollo MockedProvider mocks for repeated query consumption. Prefer adding `maxUsageCount` to the existing mock or using `newData` for reusable responses to keep tests deterministic and reduce drift.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4622
File: src/screens/OrgPost/OrgPost.tsx:109-122
Timestamp: 2025-11-08T18:14:54.607Z
Learning: In src/screens/OrgPost/OrgPost.tsx, the refetchPinnedPosts function from the ORGANIZATION_PINNED_POST_LIST query is intentionally left commented out because the entire page is set to reload when posts are deleted, unpinned, or pinned, making a separate refetch unnecessary.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/components/SuperAdminScreen/SuperAdminScreen.spec.tsx:0-0
Timestamp: 2025-01-26T12:47:50.063Z
Learning: In the talawa-admin project, tests must use the custom `useLocalStorage` hook from 'utils/useLocalstorage' instead of the native localStorage API, as the test environment doesn't have direct access to browser's localStorage.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:155-157
Timestamp: 2025-04-20T07:34:29.946Z
Learning: The user prefers to structure tests by first checking if components render any elements at all (using general assertions), before proceeding to test specific content.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.tsx:1-1
Timestamp: 2025-02-14T07:58:36.111Z
Learning: When refactoring large React components in talawa-admin, consider the complexity of state management before splitting. If the component has tightly coupled state (like forms with frequent updates), keeping it as a single component might be more maintainable than introducing complex state management across multiple components.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/style/app-fixed.module.css:1794-1802
Timestamp: 2025-04-20T06:46:50.275Z
Learning: In the advertisement component's CSS, `overflow: hidden` is intentionally used in the `.rowAdvertisements` class to maintain the grid layout structure and prevent content overflow.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/style/app-fixed.module.css:1781-1783
Timestamp: 2025-04-20T06:43:14.449Z
Learning: For the advertisement container component, adding a max-width constraint causes issues on larger screens, so using `width: auto;` without max-width is the preferred approach to allow content to properly expand as needed.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:81-0
Timestamp: 2025-08-20T18:04:43.560Z
Learning: In src/screens/OrgList/OrgList.tsx, the useDebounce hook implementation is kept inline rather than extracted to a utilities file because the pagination logic was directly extracted from the user's orglist page without modifications to maintain consistency between the admin and user implementations.

Learnt from: Piyushk8
Repo: PalisadoesFoundation/talawa-admin PR: 3877
File: src/GraphQl/Queries/OrganizationQueries.ts:133-166
Timestamp: 2025-03-25T14:28:21.436Z
Learning: The user plans to address pagination inconsistencies and consolidate duplicate GraphQL queries (like USER_JOINED_ORGANIZATIONS_PG) in a future PR focused specifically on pagination fixes across the application.

Learnt from: raggettii
Repo: PalisadoesFoundation/talawa-admin PR: 2629
File: src/screens/UserPortal/LeaveOrganization/LeaveOrganization.tsx:30-36
Timestamp: 2024-12-09T21:12:47.916Z
Learning: When modifying organization membership, prefer using Apollo's `refetchQueries` or cache updates to refresh the UI instead of using `window.location.reload()`.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4068
File: src/GraphQl/Queries/Queries.ts:636-644
Timestamp: 2025-08-08T08:14:51.613Z
Learning: In the talawa-admin project, GraphQL queries that call organization(input: { id }) expect the variable $id to be typed as String! (not ID!). Keep $id: String! for queries like GET_ORGANIZATION_BASIC_DATA, GET_ORGANIZATION_MEMBERS_PG, and GET_ORGANIZATION_POSTS_PG in src/GraphQl/Queries/Queries.ts.

Learnt from: hustlernik
Repo: PalisadoesFoundation/talawa-admin PR: 3534
File: src/GraphQl/Queries/Queries.ts:388-395
Timestamp: 2025-02-07T13:00:35.500Z
Learning: The `GET_ORGANIZATION_POSTS_PG` query is designed to fetch only a few recent posts using the `first` parameter, and pagination is intentionally omitted as it's not required for this use case.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2397
File: src/screens/OrganizationActionItems/testObject.mocks.ts:184-402
Timestamp: 2024-11-01T12:54:20.857Z
Learning: In `src/screens/OrganizationActionItems/testObject.mocks.ts`, test failures are not dependent on the `createdAt` fields; hardcoded dates in `createdAt` fields do not cause test failures in this file.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.spec.tsx:56-56
Timestamp: 2025-02-13T15:53:26.623Z
Learning: The useLocalStorage hook's setItem function in talawa-admin accepts two arguments: key and value.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4040
File: cypress/pageObjects/AdminPortal/PeoplePage.ts:30-34
Timestamp: 2025-08-13T06:52:48.055Z
Learning: In the talawa-admin project's Cypress tests, specifically in cypress/pageObjects/AdminPortal/PeoplePage.ts, the element '[data-testid="existingUser"]' is a toggle control that requires .trigger('click') instead of .click() because it's not a standard button but a custom UI component that needs direct event triggering.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2425
File: src/screens/MemberDetail/MemberDetail.test.tsx:100-100
Timestamp: 2024-11-11T07:47:39.266Z
Learning: In `src/screens/MemberDetail/MemberDetail.test.tsx`, using `await wait();` is acceptable to wait for the render to complete.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:0-0
Timestamp: 2025-08-20T18:04:52.324Z
Learning: In PR #4094, the user confirmed that the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications for initial implementation, with plans to refactor for consistency later.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.tsx:1-1
Timestamp: 2025-02-14T07:58:36.111Z
Learning: When refactoring large React components in talawa-admin, consider the complexity of state management before splitting. If the component has tightly coupled state (like forms with frequent updates), keeping it as a single component might be more maintainable than introducing complex state management across multiple components.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4040
File: cypress/pageObjects/AdminPortal/PeoplePage.ts:30-34
Timestamp: 2025-08-13T06:52:48.055Z
Learning: In the talawa-admin project's Cypress tests, specifically in cypress/pageObjects/AdminPortal/PeoplePage.ts, the element '[data-testid="existingUser"]' is a toggle control that requires .trigger('click') instead of .click() because it's not a standard button but a custom UI component that needs direct event triggering.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/Requests/Requests.spec.tsx:0-0
Timestamp: 2025-10-22T22:22:27.696Z
Learning: In talawa-admin tests using react-infinite-scroll-component (e.g., src/screens/Requests/Requests.spec.tsx), jsdom scroll is flaky. Prefer a resilient approach: try querying the container via document.querySelector('[data-testid="infinite-scroll-component"]') and fall back to window scroll if missing. Strengthen assertions by checking for page-2 items (e.g., "User9 Test") to ensure fetchMore actually ran instead of relying only on row counts.

Learnt from: bitbard3
Repo: PalisadoesFoundation/talawa-admin PR: 2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:155-162
Timestamp: 2024-12-03T05:52:37.888Z
Learning: In the `ChangeLanguageDropdown` component (`src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.tsx`), error handling has not been implemented. Therefore, test cases in `src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx` do not cover error scenarios related to error handling.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3491
File: src/components/UserPortal/SecuredRouteForUser/SecuredRouteForUser.tsx:34-43
Timestamp: 2025-02-06T20:56:05.378Z
Learning: In SecuredRouteForUser component, token updates between role switches (e.g., user to superAdmin) are better handled using separate useEffect hooks - one for initial token setup (empty deps) and another for refetch on token changes, rather than combining them into a single effect.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx:1-28
Timestamp: 2024-10-30T12:01:40.366Z
Learning: In the `MockAddPeopleToTag` component in `src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx`, it's acceptable to implement only the necessary props from `InterfaceAddPeopleToTagProps` and omit others like `refetchAssignedMembersData`, `t`, and `tCommon` that are tested separately.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/AddPeopleToTag/AddPeopleToTag.test.tsx:177-241
Timestamp: 2024-11-02T07:48:36.443Z
Learning: In `src/components/AddPeopleToTag/AddPeopleToTag.test.tsx`, prefer keeping test cases separate and more readable, even if it involves some duplication, instead of extracting common logic into helper functions.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2425
File: src/screens/MemberDetail/MemberDetail.test.tsx:100-100
Timestamp: 2024-11-11T07:47:39.266Z
Learning: In `src/screens/MemberDetail/MemberDetail.test.tsx`, using `await wait();` is acceptable to wait for the render to complete.

Learnt from: MayankJha014
Repo: PalisadoesFoundation/talawa-admin PR: 3946
File: src/components/UserPortal/ChatRoom/ChatRoom.spec.tsx:5670-5693
Timestamp: 2025-04-27T10:59:45.144Z
Learning: When testing UI components that display user names, test for firstName and lastName separately rather than as a combined full name, as the UI might render these in separate DOM elements, making combined assertions brittle.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/screens/OrganizationTags/OrganizationTags.test.tsx:184-0
Timestamp: 2024-11-02T07:18:39.563Z
Learning: In the `talawa-admin` project, it's acceptable for test cases in `src/screens/OrganizationTags/OrganizationTags.test.tsx` to test multiple behaviors within a single test function without needing to split them into smaller, focused tests.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/components/LeftDrawerOrg/LeftDrawerOrg.test.tsx:282-282
Timestamp: 2024-09-29T06:51:31.295Z
Learning: In the test 'Component should be rendered properly' within 'Testing LeftDrawerOrg component for SUPERADMIN', setting 'SuperAdmin' to false is intentional.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-01T16:34:10.347Z
Learning: In talawa-admin parallel test sharding (PR #4565), Bootstrap modals render via portals to document.body, causing screen.getByRole('dialog') to find dialogs from ALL concurrent test shards. Solution: use unique data-testid per modal instance and query within that scope using within() helper, or use findAllByTestId and take last element (less robust, timing-dependent).

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:155-157
Timestamp: 2025-04-20T07:34:29.946Z
Learning: The user prefers to structure tests by first checking if components render any elements at all (using general assertions), before proceeding to test specific content.

Learnt from: aditya-bansal-7
Repo: PalisadoesFoundation/talawa-admin PR: 2459
File: src/screens/UserPortal/People/People.test.tsx:226-242
Timestamp: 2024-11-24T19:35:45.258Z
Learning: In the `People` component, roles are not displayed in the table, so tests related to role display should account for this.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/screens/UserPortal/Organizations/Organizations.spec.tsx:19-19
Timestamp: 2025-01-26T12:32:45.867Z
Learning: In React test files, avoid using React hooks outside component scope (including in static objects like mock data). Instead, initialize hooks inside describe blocks or extract the needed functionality without using hooks.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3712
File: src/components/EventCalender/Yearly/YearlyEventCalender.spec.tsx:113-127
Timestamp: 2025-02-20T13:35:01.218Z
Learning: In React component tests, when testing window resize event handling, it's acceptable to only verify that the event is properly triggered without assertions if the test's focus is specifically on event handling rather than responsive behavior. Testing the actual responsive rendering would be a separate test case.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:367-0
Timestamp: 2024-11-02T07:32:43.099Z
Learning: In `src/components/TagActions/TagActions.tsx`, fragments around parentheses in the ancestor tags display are acceptable and should not be flagged as unnecessary.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4077
File: package.json:189-213
Timestamp: 2025-08-17T07:39:34.255Z
Learning: The Talawa Admin codebase primarily uses .spec.tsx/.spec.ts naming convention for unit tests, with Cypress tests using .cy.ts pattern. However, there is at least one .test.tsx file in the codebase, so NYC exclude patterns should include both .spec and .test patterns.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:251-274
Timestamp: 2024-10-28T06:33:09.726Z
Learning: In `TagActions.test.tsx`, negative test cases for tag operations can be deferred and added later if necessary, according to the team's plan.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/components/TagActions/TagNode.tsx:174-176
Timestamp: 2024-10-30T15:29:21.628Z
Learning: In `src/components/TagActions/TagNode.tsx`, the `hasMore` prop in `InfiniteScroll` is correctly implemented, handling undefined data safely with optional chaining and nullish coalescing, and the infinite scrolling functionality is thoroughly tested.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:123-131
Timestamp: 2024-10-28T06:38:43.765Z
Learning: In `TagActions.test.tsx`, `link2` is the error link used to simulate errors, so the existing test cases sufficiently cover error handling.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/screens/MemberDetail/MemberDetail.test.tsx:170-195
Timestamp: 2024-10-08T16:13:41.996Z
Learning: In unit tests for this project, direct `click()` calls are acceptable; avoid suggesting replacing them with `userEvent.click()`.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/Advertisements.spec.tsx:316-327
Timestamp: 2025-04-20T06:41:55.660Z
Learning: In the Talawa Admin project's test files, button click events may trigger asynchronous operations that require awaiting the act() call, even when using fireEvent.click() which is typically synchronous.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 2482
File: src/components/AddOn/support/components/Action/Action.spec.tsx:1-8
Timestamp: 2024-11-27T06:37:47.871Z
Learning: In the Talawa-Admin project, the `testing-library/jest-dom` package is imported globally in `vitest.setup.ts`, so individual test files do not need to import it separately.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/components/SuperAdminScreen/SuperAdminScreen.spec.tsx:0-0
Timestamp: 2025-01-26T12:47:50.063Z
Learning: In the talawa-admin project, tests must use the custom `useLocalStorage` hook from 'utils/useLocalstorage' instead of the native localStorage API, as the test environment doesn't have direct access to browser's localStorage.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2718
File: src/screens/UserPortal/Settings/Settings.spec.tsx:0-0
Timestamp: 2024-12-22T17:58:17.818Z
Learning: The matchMedia mock implementation in `Settings.spec.tsx` no longer includes the deprecated addListener and removeListener methods, opting solely for addEventListener and removeEventListener.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 3569
File: src/screens/UserPortal/Settings/Settings.spec.tsx:314-316
Timestamp: 2025-02-09T06:22:23.028Z
Learning: In the Settings component's tests, `fireEvent.change` should be used instead of `userEvent.type` for the address input field, as `userEvent` doesn't work correctly in this case.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: public/locales/zh/translation.json:0-0
Timestamp: 2025-03-19T17:42:16.729Z
Learning: The PR #3814 focuses specifically on implementing sign up, sign in, sign out, and useSession in better auth (frontend), and translation changes in the Chinese localization file were not part of the intentional changes made by the author.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3988
File: cypress/e2e/admin_spec/people.cy.ts:25-33
Timestamp: 2025-07-02T19:15:13.036Z
Learning: In the talawa-admin project, specifically in cypress/e2e/admin_spec/people.cy.ts, the user syedali237 intentionally designed the "add an existing member" and "delete a member" tests to work simultaneously with interdependencies, where the delete test relies on the add test having run first.

Learnt from: MayankJha014
Repo: PalisadoesFoundation/talawa-admin PR: 3946
File: src/components/UserPortal/ChatRoom/ChatRoom.spec.tsx:0-0
Timestamp: 2025-04-27T04:35:39.472Z
Learning: In the talawa-admin codebase tests, to check whether toast notifications were called, use the imported toast object directly with waitFor (e.g., `expect(toast.error).toHaveBeenCalled()`). Do not use require() style imports within test assertions.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.spec.tsx:403-421
Timestamp: 2025-04-20T06:45:57.175Z
Learning: In the talawa-admin project, the Advertisement component tests (3 files) use both ApolloProvider and MockedProvider together, though it's not a widespread pattern in the codebase. The maintainer has confirmed this approach is needed for these specific tests.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-17T22:18:09.680Z
Learning: Talawa Admin Phase 2A testing guideline: Allow vi.hoisted() + vi.mock() module-level mocks for shared dependencies; prefer afterEach(() => vi.clearAllMocks()) as default cleanup. Use afterEach(() => vi.restoreAllMocks()) only in suites that create vi.spyOn spies or patch real implementations. Avoid vi.resetAllMocks() globally. The generic “no module-level mocks” rule is updated to “no module-level vi.fn except vi.hoisted module mocks.”

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-12T00:28:53.713Z
Learning: In talawa-admin PR #4565 continuation (PR #4664 planned), Phase 2A mock isolation strategy uses global vi.clearAllMocks() in afterEach (vitest.setup.ts) plus refactoring module-level vi.fn() into per-test beforeEach blocks across 6 parallelizable issues (2A.0 foundation, 2A.1-2A.4 directory-based fixes, 2A.5 validation). This approach addresses mock call history accumulation enabling maxConcurrency: 2 and 2.3-2.5x speedup. vi.restoreAllMocks() alternative considered for spy restoration during validation phase. Phase 2A (mocks) correctly separated from Phase 2B (DOM/Apollo).

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementRegister/AdvertisementRegister.spec.tsx:403-421
Timestamp: 2025-04-20T06:45:57.175Z
Learning: Using both ApolloProvider and MockedProvider together in tests is an established pattern in this codebase, even though it's technically redundant from Apollo Client's best practices perspective.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-11T11:51:09.236Z
Learning: In talawa-admin PR #4664 (continuation of PR #4565 sharding work), global mock cleanup was implemented via vi.clearAllMocks() in vitest.setup.ts afterEach, along with Apollo Client warning suppression (temporary, pending follow-up PR) and test suite refactoring to per-test StaticMockLink instances. This test isolation strategy addresses mock state leakage that forced maxConcurrency: 1 in PR #4565, enabling future parallel test execution improvements and 3-4x speedup potential.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:409-0
Timestamp: 2025-08-20T18:04:34.194Z
Learning: In PR #4094, the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modification for initial implementation, with plans to refactor for consistency later.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:0-0
Timestamp: 2025-08-20T18:04:52.324Z
Learning: In PR #4094, the user confirmed that the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications for initial implementation, with plans to refactor for consistency later.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:435-0
Timestamp: 2025-08-20T18:04:23.118Z
Learning: In the talawa-admin codebase, pagination logic for the admin orglist page in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications to maintain consistency between the two implementations.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4419
File: src/components/ProfileCard/ProfileCard.spec.tsx:112-131
Timestamp: 2025-10-12T21:51:10.123Z
Learning: In the ProfileCard component (`src/components/ProfileCard/ProfileCard.tsx`), when an image load error occurs, the component only sets the image's `display: 'none'` style and does not render the Avatar component with "dummy picture" alt text. The Avatar component is only rendered when `userImage` is falsy or equals 'null', not when the image fails to load.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts:0-0
Timestamp: 2025-10-22T22:00:53.943Z
Learning: In src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts (and similar mock files), avoid duplicating identical Apollo MockedProvider mocks for repeated query consumption. Prefer adding `maxUsageCount` to the existing mock or using `newData` for reusable responses to keep tests deterministic and reduce drift.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTag.tsx:58-97
Timestamp: 2024-10-30T13:38:29.300Z
Learning: In the `ManageTag` component (`src/screens/ManageTag/ManageTag.tsx`), extracting modal state management to a custom hook may require additional state modifications for the `toggle` and `show` functions.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:81-0
Timestamp: 2025-08-20T18:04:43.560Z
Learning: In src/screens/OrgList/OrgList.tsx, the useDebounce hook implementation is kept inline rather than extracted to a utilities file because the pagination logic was directly extracted from the user's orglist page without modifications to maintain consistency between the admin and user implementations.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2397
File: src/screens/UserPortal/Volunteer/Actions/Actions.tsx:367-374
Timestamp: 2024-11-01T16:18:01.545Z
Learning: In the `src/screens/UserPortal/Volunteer/Actions/Actions.tsx` file, the search button intentionally includes `tabIndex={-1}`. This is acceptable for our application, and future reviews should not flag this as an accessibility concern.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:216-0
Timestamp: 2024-11-02T07:31:50.788Z
Learning: In `src/components/TagActions/TagActions.tsx`, the submit button should not be disabled when no tags are selected, as per the design preference.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagNode.tsx:129-137
Timestamp: 2024-10-28T08:21:01.364Z
Learning: When setting the aria-label for the checkbox in `TagNode.tsx`, it's acceptable to use `t('selectTag')` without including the tag name.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.tsx:110-147
Timestamp: 2024-10-28T06:51:05.867Z
Learning: When handling the `useEffect` hooks for `addAncestorTagsData` and `removeAncestorTagsData` in `TagActions.tsx`, it's preferred to keep them separate to avoid confusion and enhance readability.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2680
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:528-712
Timestamp: 2024-12-22T07:43:26.168Z
Learning: You prefer to keep migrated tests even if they appear duplicated because they originated from the old AdvertisementEntry.test.tsx file.

Learnt from: bitbard3
Repo: PalisadoesFoundation/talawa-admin PR: 2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:145-155
Timestamp: 2024-12-02T04:20:11.745Z
Learning: In PRs focused solely on refactoring test cases from Jest to Vitest, avoid suggesting optimizations or changes outside the migration scope.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/OrganizationTags/OrganizationTags.tsx:350-376
Timestamp: 2024-10-30T13:18:56.627Z
Learning: In the `src/screens/OrganizationTags/OrganizationTags.tsx` file, the `OrganizationTags` component uses chunk size with the `InfiniteScroll` component and an outer parent div for handling data loading and scrolling.

Learnt from: Piyushk8
Repo: PalisadoesFoundation/talawa-admin PR: 3877
File: src/GraphQl/Queries/OrganizationQueries.ts:133-166
Timestamp: 2025-03-25T14:28:21.436Z
Learning: The user plans to address pagination inconsistencies and consolidate duplicate GraphQL queries (like USER_JOINED_ORGANIZATIONS_PG) in a future PR focused specifically on pagination fixes across the application.

Learnt from: PratapRathi
Repo: PalisadoesFoundation/talawa-admin PR: 3923
File: src/GraphQl/Queries/Queries.ts:62-73
Timestamp: 2025-04-09T05:00:49.395Z
Learning: The ORGANIZATION_LIST_BY_SEARCH query in src/GraphQl/Queries/Queries.ts relies on search filtering rather than pagination to manage result set size, with the team planning to add limits later if needed.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4622
File: src/screens/OrgPost/OrgPost.tsx:109-122
Timestamp: 2025-11-08T18:14:54.607Z
Learning: In src/screens/OrgPost/OrgPost.tsx, the refetchPinnedPosts function from the ORGANIZATION_PINNED_POST_LIST query is intentionally left commented out because the entire page is set to reload when posts are deleted, unpinned, or pinned, making a separate refetch unnecessary.

Learnt from: raggettii
Repo: PalisadoesFoundation/talawa-admin PR: 2629
File: src/screens/UserPortal/LeaveOrganization/LeaveOrganization.tsx:30-36
Timestamp: 2024-12-09T21:12:47.916Z
Learning: When modifying organization membership, prefer using Apollo's `refetchQueries` or cache updates to refresh the UI instead of using `window.location.reload()`.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/OrganizationTags/OrganizationTags.tsx:370-373
Timestamp: 2024-10-30T13:16:35.635Z
Learning: In `src/screens/OrganizationTags/OrganizationTags.tsx`, when mapping rows for the DataGrid, use `index + 1` as the `id` because the index number plus one is required.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4068
File: src/GraphQl/Queries/Queries.ts:636-644
Timestamp: 2025-08-08T08:14:51.613Z
Learning: In the talawa-admin project, GraphQL queries that call organization(input: { id }) expect the variable $id to be typed as String! (not ID!). Keep $id: String! for queries like GET_ORGANIZATION_BASIC_DATA, GET_ORGANIZATION_MEMBERS_PG, and GET_ORGANIZATION_POSTS_PG in src/GraphQl/Queries/Queries.ts.

Learnt from: hustlernik
Repo: PalisadoesFoundation/talawa-admin PR: 3534
File: src/GraphQl/Queries/Queries.ts:388-395
Timestamp: 2025-02-07T13:00:35.500Z
Learning: The `GET_ORGANIZATION_POSTS_PG` query is designed to fetch only a few recent posts using the `first` parameter, and pagination is intentionally omitted as it's not required for this use case.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:0-0
Timestamp: 2025-08-20T18:04:52.324Z
Learning: In PR #4094, the user confirmed that the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications for initial implementation, with plans to refactor for consistency later.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.tsx:1-1
Timestamp: 2025-02-14T07:58:36.111Z
Learning: When refactoring large React components in talawa-admin, consider the complexity of state management before splitting. If the component has tightly coupled state (like forms with frequent updates), keeping it as a single component might be more maintainable than introducing complex state management across multiple components.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:435-0
Timestamp: 2025-08-20T18:04:23.118Z
Learning: In the talawa-admin codebase, pagination logic for the admin orglist page in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications to maintain consistency between the two implementations.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3491
File: src/components/UserPortal/SecuredRouteForUser/SecuredRouteForUser.tsx:34-43
Timestamp: 2025-02-06T20:56:05.378Z
Learning: In SecuredRouteForUser component, token updates between role switches (e.g., user to superAdmin) are better handled using separate useEffect hooks - one for initial token setup (empty deps) and another for refetch on token changes, rather than combining them into a single effect.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:367-0
Timestamp: 2024-11-02T07:32:43.099Z
Learning: In `src/components/TagActions/TagActions.tsx`, fragments around parentheses in the ancestor tags display are acceptable and should not be flagged as unnecessary.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2397
File: src/screens/UserPortal/Volunteer/Actions/Actions.tsx:367-374
Timestamp: 2024-11-01T16:18:01.545Z
Learning: In the `src/screens/UserPortal/Volunteer/Actions/Actions.tsx` file, the search button intentionally includes `tabIndex={-1}`. This is acceptable for our application, and future reviews should not flag this as an accessibility concern.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:229-252
Timestamp: 2024-06-30T21:44:02.495Z
Learning: When adding keyboard events for accessibility, consider potential user confusion and unintended navigations. Explore alternative approaches like tooltips or visual indicators to inform users about keyboard functionalities.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.tsx:110-147
Timestamp: 2024-10-28T06:51:05.867Z
Learning: When handling the `useEffect` hooks for `addAncestorTagsData` and `removeAncestorTagsData` in `TagActions.tsx`, it's preferred to keep them separate to avoid confusion and enhance readability.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:265-275
Timestamp: 2024-10-08T16:13:41.996Z
Learning: When suggesting adding keyboard events for accessibility, consider potential user confusion and explore alternative approaches like tooltips or visual indicators to balance accessibility and user experience.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 3915
File: src/screens/LoginPage/LoginPage.tsx:458-459
Timestamp: 2025-04-05T08:30:08.858Z
Learning: The "adminLogin" translation key is used in LoginPage.tsx and should be present in translation.json files for all languages, not in common.json or errors.json files. The key is accessed using the t() function, not tCommon().

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagNode.tsx:129-137
Timestamp: 2024-10-28T08:21:01.364Z
Learning: When setting the aria-label for the checkbox in `TagNode.tsx`, it's acceptable to use `t('selectTag')` without including the tag name.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4760
File: src/utils/adminPluginInstaller.ts:256-260
Timestamp: 2025-11-23T12:02:06.471Z
Learning: In PalisadoesFoundation/talawa-admin, the CREATE_PLUGIN_MUTATION in src/utils/adminPluginInstaller.ts uses message string matching (checking for "already exists") to detect duplicate plugin errors because the backend doesn't currently expose structured error codes for this mutation. This is a known limitation that could be improved in the future with typed error responses from the API.

Learnt from: bitbard3
Repo: PalisadoesFoundation/talawa-admin PR: 2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:155-162
Timestamp: 2024-12-03T05:52:37.888Z
Learning: In the `ChangeLanguageDropdown` component (`src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.tsx`), error handling has not been implemented. Therefore, test cases in `src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx` do not cover error scenarios related to error handling.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:251-274
Timestamp: 2024-10-28T06:33:09.726Z
Learning: In `TagActions.test.tsx`, negative test cases for tag operations can be deferred and added later if necessary, according to the team's plan.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/Requests/Requests.spec.tsx:0-0
Timestamp: 2025-10-22T22:22:27.696Z
Learning: In talawa-admin tests using react-infinite-scroll-component (e.g., src/screens/Requests/Requests.spec.tsx), jsdom scroll is flaky. Prefer a resilient approach: try querying the container via document.querySelector('[data-testid="infinite-scroll-component"]') and fall back to window scroll if missing. Strengthen assertions by checking for page-2 items (e.g., "User9 Test") to ensure fetchMore actually ran instead of relying only on row counts.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2718
File: src/screens/UserPortal/Settings/Settings.spec.tsx:0-0
Timestamp: 2024-12-22T17:58:17.818Z
Learning: The matchMedia mock implementation in `Settings.spec.tsx` no longer includes the deprecated addListener and removeListener methods, opting solely for addEventListener and removeEventListener.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/AddPeopleToTag/AddPeopleToTag.test.tsx:177-241
Timestamp: 2024-11-02T07:48:36.443Z
Learning: In `src/components/AddPeopleToTag/AddPeopleToTag.test.tsx`, prefer keeping test cases separate and more readable, even if it involves some duplication, instead of extracting common logic into helper functions.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2680
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:528-712
Timestamp: 2024-12-22T07:43:26.168Z
Learning: You prefer to keep migrated tests even if they appear duplicated because they originated from the old AdvertisementEntry.test.tsx file.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts:0-0
Timestamp: 2025-10-22T22:00:53.943Z
Learning: In src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts (and similar mock files), avoid duplicating identical Apollo MockedProvider mocks for repeated query consumption. Prefer adding `maxUsageCount` to the existing mock or using `newData` for reusable responses to keep tests deterministic and reduce drift.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:123-131
Timestamp: 2024-10-28T06:38:43.765Z
Learning: In `TagActions.test.tsx`, `link2` is the error link used to simulate errors, so the existing test cases sufficiently cover error handling.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/screens/MemberDetail/MemberDetail.test.tsx:170-195
Timestamp: 2024-10-08T16:13:41.996Z
Learning: In unit tests for this project, direct `click()` calls are acceptable; avoid suggesting replacing them with `userEvent.click()`.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4040
File: cypress/pageObjects/AdminPortal/PeoplePage.ts:30-34
Timestamp: 2025-08-13T06:52:48.055Z
Learning: In the talawa-admin project's Cypress tests, specifically in cypress/pageObjects/AdminPortal/PeoplePage.ts, the element '[data-testid="existingUser"]' is a toggle control that requires .trigger('click') instead of .click() because it's not a standard button but a custom UI component that needs direct event triggering.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/screens/UserPortal/Organizations/Organizations.spec.tsx:19-19
Timestamp: 2025-01-26T12:32:45.867Z
Learning: In React test files, avoid using React hooks outside component scope (including in static objects like mock data). Instead, initialize hooks inside describe blocks or extract the needed functionality without using hooks.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/components/LeftDrawerOrg/LeftDrawerOrg.test.tsx:282-282
Timestamp: 2024-09-29T06:51:31.295Z
Learning: In the test 'Component should be rendered properly' within 'Testing LeftDrawerOrg component for SUPERADMIN', setting 'SuperAdmin' to false is intentional.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/screens/OrganizationTags/OrganizationTags.test.tsx:184-0
Timestamp: 2024-11-02T07:18:39.563Z
Learning: In the `talawa-admin` project, it's acceptable for test cases in `src/screens/OrganizationTags/OrganizationTags.test.tsx` to test multiple behaviors within a single test function without needing to split them into smaller, focused tests.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx:1-28
Timestamp: 2024-10-30T12:01:40.366Z
Learning: In the `MockAddPeopleToTag` component in `src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx`, it's acceptable to implement only the necessary props from `InterfaceAddPeopleToTagProps` and omit others like `refetchAssignedMembersData`, `t`, and `tCommon` that are tested separately.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3712
File: src/components/EventCalender/Yearly/YearlyEventCalender.spec.tsx:113-127
Timestamp: 2025-02-20T13:35:01.218Z
Learning: In React component tests, when testing window resize event handling, it's acceptable to only verify that the event is properly triggered without assertions if the test's focus is specifically on event handling rather than responsive behavior. Testing the actual responsive rendering would be a separate test case.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:216-0
Timestamp: 2024-11-02T07:31:50.788Z
Learning: In `src/components/TagActions/TagActions.tsx`, the submit button should not be disabled when no tags are selected, as per the design preference.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3491
File: src/components/UserPortal/SecuredRouteForUser/SecuredRouteForUser.tsx:34-43
Timestamp: 2025-02-06T20:56:05.378Z
Learning: In SecuredRouteForUser component, token updates between role switches (e.g., user to superAdmin) are better handled using separate useEffect hooks - one for initial token setup (empty deps) and another for refetch on token changes, rather than combining them into a single effect.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTag.tsx:58-97
Timestamp: 2024-10-30T13:38:29.300Z
Learning: In the `ManageTag` component (`src/screens/ManageTag/ManageTag.tsx`), extracting modal state management to a custom hook may require additional state modifications for the `toggle` and `show` functions.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4419
File: src/components/ProfileCard/ProfileCard.spec.tsx:112-131
Timestamp: 2025-10-12T21:51:10.123Z
Learning: In the ProfileCard component (`src/components/ProfileCard/ProfileCard.tsx`), when an image load error occurs, the component only sets the image's `display: 'none'` style and does not render the Avatar component with "dummy picture" alt text. The Avatar component is only rendered when `userImage` is falsy or equals 'null', not when the image fails to load.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:81-0
Timestamp: 2025-08-20T18:04:43.560Z
Learning: In src/screens/OrgList/OrgList.tsx, the useDebounce hook implementation is kept inline rather than extracted to a utilities file because the pagination logic was directly extracted from the user's orglist page without modifications to maintain consistency between the admin and user implementations.

Learnt from: Aad1tya27
Repo: PalisadoesFoundation/talawa-admin PR: 3255
File: src/screens/UserPortal/Chat/Chat.tsx:0-0
Timestamp: 2025-01-12T16:25:38.818Z
Learning: In the Chat component of talawa-admin, the `chats` state is initialized with an empty array by default using `useState<Chat[]>([])`, making explicit empty array assignments in else conditions unnecessary.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/style/app-fixed.module.css:9292-9297
Timestamp: 2025-04-20T06:48:56.163Z
Learning: Focus styles for dropdown buttons in the Advertisement component are considered optional by the team, as indicated by declining to add `:focus-visible` styles to `.dropdownButton` class.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:0-0
Timestamp: 2025-08-20T18:04:52.324Z
Learning: In PR #4094, the user confirmed that the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications for initial implementation, with plans to refactor for consistency later.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.tsx:1-1
Timestamp: 2025-02-14T07:58:36.111Z
Learning: When refactoring large React components in talawa-admin, consider the complexity of state management before splitting. If the component has tightly coupled state (like forms with frequent updates), keeping it as a single component might be more maintainable than introducing complex state management across multiple components.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.tsx:1-1
Timestamp: 2025-02-14T07:49:53.498Z
Learning: The Settings component in talawa-admin should be split into smaller components and custom hooks to maintain code quality and meet line limit requirements. Key sections to extract: PersonalInfoSection, ContactInfoSection, and form logic hooks.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3491
File: src/components/UserPortal/SecuredRouteForUser/SecuredRouteForUser.tsx:34-43
Timestamp: 2025-02-06T20:56:05.378Z
Learning: In SecuredRouteForUser component, token updates between role switches (e.g., user to superAdmin) are better handled using separate useEffect hooks - one for initial token setup (empty deps) and another for refetch on token changes, rather than combining them into a single effect.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTag.tsx:58-97
Timestamp: 2024-10-30T13:38:29.300Z
Learning: In the `ManageTag` component (`src/screens/ManageTag/ManageTag.tsx`), extracting modal state management to a custom hook may require additional state modifications for the `toggle` and `show` functions.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.tsx:110-147
Timestamp: 2024-10-28T06:51:05.867Z
Learning: When handling the `useEffect` hooks for `addAncestorTagsData` and `removeAncestorTagsData` in `TagActions.tsx`, it's preferred to keep them separate to avoid confusion and enhance readability.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4419
File: src/components/ProfileCard/ProfileCard.spec.tsx:112-131
Timestamp: 2025-10-12T21:51:10.123Z
Learning: In the ProfileCard component (`src/components/ProfileCard/ProfileCard.tsx`), when an image load error occurs, the component only sets the image's `display: 'none'` style and does not render the Avatar component with "dummy picture" alt text. The Avatar component is only rendered when `userImage` is falsy or equals 'null', not when the image fails to load.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:81-0
Timestamp: 2025-08-20T18:04:43.560Z
Learning: In src/screens/OrgList/OrgList.tsx, the useDebounce hook implementation is kept inline rather than extracted to a utilities file because the pagination logic was directly extracted from the user's orglist page without modifications to maintain consistency between the admin and user implementations.

Learnt from: Aad1tya27
Repo: PalisadoesFoundation/talawa-admin PR: 3255
File: src/screens/UserPortal/Chat/Chat.tsx:0-0
Timestamp: 2025-01-12T16:25:38.818Z
Learning: In the Chat component of talawa-admin, the `chats` state is initialized with an empty array by default using `useState<Chat[]>([])`, making explicit empty array assignments in else conditions unnecessary.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/components/LeftDrawerOrg/LeftDrawerOrg.test.tsx:282-282
Timestamp: 2024-09-29T06:51:31.295Z
Learning: In the test 'Component should be rendered properly' within 'Testing LeftDrawerOrg component for SUPERADMIN', setting 'SuperAdmin' to false is intentional.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:367-0
Timestamp: 2024-11-02T07:32:43.099Z
Learning: In `src/components/TagActions/TagActions.tsx`, fragments around parentheses in the ancestor tags display are acceptable and should not be flagged as unnecessary.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2397
File: src/screens/UserPortal/Volunteer/Actions/Actions.tsx:367-374
Timestamp: 2024-11-01T16:18:01.545Z
Learning: In the `src/screens/UserPortal/Volunteer/Actions/Actions.tsx` file, the search button intentionally includes `tabIndex={-1}`. This is acceptable for our application, and future reviews should not flag this as an accessibility concern.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:229-252
Timestamp: 2024-06-30T21:44:02.495Z
Learning: When adding keyboard events for accessibility, consider potential user confusion and unintended navigations. Explore alternative approaches like tooltips or visual indicators to inform users about keyboard functionalities.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:265-275
Timestamp: 2024-10-08T16:13:41.996Z
Learning: When suggesting adding keyboard events for accessibility, consider potential user confusion and explore alternative approaches like tooltips or visual indicators to balance accessibility and user experience.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 3915
File: src/screens/LoginPage/LoginPage.tsx:458-459
Timestamp: 2025-04-05T08:30:08.858Z
Learning: The "adminLogin" translation key is used in LoginPage.tsx and should be present in translation.json files for all languages, not in common.json or errors.json files. The key is accessed using the t() function, not tCommon().

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagNode.tsx:129-137
Timestamp: 2024-10-28T08:21:01.364Z
Learning: When setting the aria-label for the checkbox in `TagNode.tsx`, it's acceptable to use `t('selectTag')` without including the tag name.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4760
File: src/utils/adminPluginInstaller.ts:256-260
Timestamp: 2025-11-23T12:02:06.471Z
Learning: In PalisadoesFoundation/talawa-admin, the CREATE_PLUGIN_MUTATION in src/utils/adminPluginInstaller.ts uses message string matching (checking for "already exists") to detect duplicate plugin errors because the backend doesn't currently expose structured error codes for this mutation. This is a known limitation that could be improved in the future with typed error responses from the API.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:216-0
Timestamp: 2024-11-02T07:31:50.788Z
Learning: In `src/components/TagActions/TagActions.tsx`, the submit button should not be disabled when no tags are selected, as per the design preference.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4094
File: src/screens/OrgList/OrgList.tsx:0-0
Timestamp: 2025-08-20T18:04:52.324Z
Learning: In PR #4094, the user confirmed that the pagination logic in src/screens/OrgList/OrgList.tsx was directly extracted from the user's orglist page without modifications for initial implementation, with plans to refactor for consistency later.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.tsx:1-1
Timestamp: 2025-02-14T07:58:36.111Z
Learning: When refactoring large React components in talawa-admin, consider the complexity of state management before splitting. If the component has tightly coupled state (like forms with frequent updates), keeping it as a single component might be more maintainable than introducing complex state management across multiple components.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-12T00:28:53.713Z
Learning: In talawa-admin PR #4565 continuation (PR #4664 planned), Phase 2A mock isolation strategy uses global vi.clearAllMocks() in afterEach (vitest.setup.ts) plus refactoring module-level vi.fn() into per-test beforeEach blocks across 6 parallelizable issues (2A.0 foundation, 2A.1-2A.4 directory-based fixes, 2A.5 validation). This approach addresses mock call history accumulation enabling maxConcurrency: 2 and 2.3-2.5x speedup. vi.restoreAllMocks() alternative considered for spy restoration during validation phase. Phase 2A (mocks) correctly separated from Phase 2B (DOM/Apollo).

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3593
File: src/screens/UserPortal/Settings/Settings.tsx:1-1
Timestamp: 2025-02-14T07:49:53.498Z
Learning: The Settings component in talawa-admin should be split into smaller components and custom hooks to maintain code quality and meet line limit requirements. Key sections to extract: PersonalInfoSection, ContactInfoSection, and form logic hooks.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:367-0
Timestamp: 2024-11-02T07:32:43.099Z
Learning: In `src/components/TagActions/TagActions.tsx`, fragments around parentheses in the ancestor tags display are acceptable and should not be flagged as unnecessary.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2397
File: src/screens/UserPortal/Volunteer/Actions/Actions.tsx:367-374
Timestamp: 2024-11-01T16:18:01.545Z
Learning: In the `src/screens/UserPortal/Volunteer/Actions/Actions.tsx` file, the search button intentionally includes `tabIndex={-1}`. This is acceptable for our application, and future reviews should not flag this as an accessibility concern.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:229-252
Timestamp: 2024-06-30T21:44:02.495Z
Learning: When adding keyboard events for accessibility, consider potential user confusion and unintended navigations. Explore alternative approaches like tooltips or visual indicators to inform users about keyboard functionalities.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.tsx:110-147
Timestamp: 2024-10-28T06:51:05.867Z
Learning: When handling the `useEffect` hooks for `addAncestorTagsData` and `removeAncestorTagsData` in `TagActions.tsx`, it's preferred to keep them separate to avoid confusion and enhance readability.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:265-275
Timestamp: 2024-10-08T16:13:41.996Z
Learning: When suggesting adding keyboard events for accessibility, consider potential user confusion and explore alternative approaches like tooltips or visual indicators to balance accessibility and user experience.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 3915
File: src/screens/LoginPage/LoginPage.tsx:458-459
Timestamp: 2025-04-05T08:30:08.858Z
Learning: The "adminLogin" translation key is used in LoginPage.tsx and should be present in translation.json files for all languages, not in common.json or errors.json files. The key is accessed using the t() function, not tCommon().

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagNode.tsx:129-137
Timestamp: 2024-10-28T08:21:01.364Z
Learning: When setting the aria-label for the checkbox in `TagNode.tsx`, it's acceptable to use `t('selectTag')` without including the tag name.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4760
File: src/utils/adminPluginInstaller.ts:256-260
Timestamp: 2025-11-23T12:02:06.471Z
Learning: In PalisadoesFoundation/talawa-admin, the CREATE_PLUGIN_MUTATION in src/utils/adminPluginInstaller.ts uses message string matching (checking for "already exists") to detect duplicate plugin errors because the backend doesn't currently expose structured error codes for this mutation. This is a known limitation that could be improved in the future with typed error responses from the API.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:216-0
Timestamp: 2024-11-02T07:31:50.788Z
Learning: In `src/components/TagActions/TagActions.tsx`, the submit button should not be disabled when no tags are selected, as per the design preference.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-12T00:28:53.713Z
Learning: In talawa-admin PR #4565 continuation (PR #4664 planned), Phase 2A mock isolation strategy uses global vi.clearAllMocks() in afterEach (vitest.setup.ts) plus refactoring module-level vi.fn() into per-test beforeEach blocks across 6 parallelizable issues (2A.0 foundation, 2A.1-2A.4 directory-based fixes, 2A.5 validation). This approach addresses mock call history accumulation enabling maxConcurrency: 2 and 2.3-2.5x speedup. vi.restoreAllMocks() alternative considered for spy restoration during validation phase. Phase 2A (mocks) correctly separated from Phase 2B (DOM/Apollo).

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2718
File: src/screens/UserPortal/Settings/Settings.spec.tsx:0-0
Timestamp: 2024-12-22T17:58:17.818Z
Learning: The matchMedia mock implementation in `Settings.spec.tsx` no longer includes the deprecated addListener and removeListener methods, opting solely for addEventListener and removeEventListener.

Learnt from: palisadoes
Repo: PalisadoesFoundation/talawa-admin PR: 4718
File: src/components/EventManagement/Dashboard/EventDashboard.mocks.ts:83-114
Timestamp: 2025-11-21T12:42:24.884Z
Learning: In talawa-admin mock files (e.g., EventDashboard.mocks.ts), mock constant names must accurately reflect what they test. Mock names suggesting role-based logic (e.g., MOCKS_WITH_ADMIN_ROLE) are misleading when the component derives role from localStorage rather than mock data. Name mocks based on their distinguishing data features (e.g., MOCKS_WITH_SINGLE_ATTENDEE) or test context (e.g., MOCKS_FOR_ADMIN_STORAGE_TEST).

Learnt from: bitbard3
Repo: PalisadoesFoundation/talawa-admin PR: 2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:155-162
Timestamp: 2024-12-03T05:52:37.888Z
Learning: In the `ChangeLanguageDropdown` component (`src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.tsx`), error handling has not been implemented. Therefore, test cases in `src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx` do not cover error scenarios related to error handling.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4882
File: src/screens/UserPortal/Volunteer/UpcomingEvents/RecurringEventVolunteerModal.spec.tsx:69-109
Timestamp: 2025-11-28T16:02:31.790Z
Learning: In Talawa Admin test files (e.g., src/screens/UserPortal/Volunteer/UpcomingEvents/RecurringEventVolunteerModal.spec.tsx), developers prefer keeping date/time mocks (like vi.spyOn(Date.prototype, 'toLocaleDateString')) inline within individual test cases rather than consolidating them in beforeEach blocks, to maintain clarity and keep mocks close to the tests that use them, even if it results in some duplication.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx:1-28
Timestamp: 2024-10-30T12:01:40.366Z
Learning: In the `MockAddPeopleToTag` component in `src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx`, it's acceptable to implement only the necessary props from `InterfaceAddPeopleToTagProps` and omit others like `refetchAssignedMembersData`, `t`, and `tCommon` that are tested separately.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts:0-0
Timestamp: 2025-10-22T22:00:53.943Z
Learning: In src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts (and similar mock files), avoid duplicating identical Apollo MockedProvider mocks for repeated query consumption. Prefer adding `maxUsageCount` to the existing mock or using `newData` for reusable responses to keep tests deterministic and reduce drift.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2397
File: src/screens/OrganizationActionItems/testObject.mocks.ts:184-402
Timestamp: 2024-11-01T12:54:20.857Z
Learning: In `src/screens/OrganizationActionItems/testObject.mocks.ts`, test failures are not dependent on the `createdAt` fields; hardcoded dates in `createdAt` fields do not cause test failures in this file.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 3915
File: src/screens/LoginPage/LoginPage.tsx:458-459
Timestamp: 2025-04-05T08:30:08.858Z
Learning: The "adminLogin" translation key is used in LoginPage.tsx and should be present in translation.json files for all languages, not in common.json or errors.json files. The key is accessed using the t() function, not tCommon().

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2425
File: src/screens/MemberDetail/MemberDetail.test.tsx:100-100
Timestamp: 2024-11-11T07:47:39.266Z
Learning: In `src/screens/MemberDetail/MemberDetail.test.tsx`, using `await wait();` is acceptable to wait for the render to complete.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/Requests/Requests.spec.tsx:0-0
Timestamp: 2025-10-22T22:22:27.696Z
Learning: In talawa-admin tests using react-infinite-scroll-component (e.g., src/screens/Requests/Requests.spec.tsx), jsdom scroll is flaky. Prefer a resilient approach: try querying the container via document.querySelector('[data-testid="infinite-scroll-component"]') and fall back to window scroll if missing. Strengthen assertions by checking for page-2 items (e.g., "User9 Test") to ensure fetchMore actually ran instead of relying only on row counts.

Learnt from: MayankJha014
Repo: PalisadoesFoundation/talawa-admin PR: 3946
File: src/components/UserPortal/ChatRoom/ChatRoom.spec.tsx:5670-5693
Timestamp: 2025-04-27T10:59:45.144Z
Learning: When testing UI components that display user names, test for firstName and lastName separately rather than as a combined full name, as the UI might render these in separate DOM elements, making combined assertions brittle.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/screens/OrganizationTags/OrganizationTags.test.tsx:184-0
Timestamp: 2024-11-02T07:18:39.563Z
Learning: In the `talawa-admin` project, it's acceptable for test cases in `src/screens/OrganizationTags/OrganizationTags.test.tsx` to test multiple behaviors within a single test function without needing to split them into smaller, focused tests.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/components/LeftDrawerOrg/LeftDrawerOrg.test.tsx:282-282
Timestamp: 2024-09-29T06:51:31.295Z
Learning: In the test 'Component should be rendered properly' within 'Testing LeftDrawerOrg component for SUPERADMIN', setting 'SuperAdmin' to false is intentional.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-01T16:34:10.347Z
Learning: In talawa-admin parallel test sharding (PR #4565), Bootstrap modals render via portals to document.body, causing screen.getByRole('dialog') to find dialogs from ALL concurrent test shards. Solution: use unique data-testid per modal instance and query within that scope using within() helper, or use findAllByTestId and take last element (less robust, timing-dependent).

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4865
File: src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.spec.tsx:261-280
Timestamp: 2025-11-27T11:40:30.747Z
Learning: In Talawa Admin tests (e.g., src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.spec.tsx), react-bootstrap Modal header close buttons don't support custom test IDs, so using getAllByRole('button', { name: /close/i })[0] to select the modal's primary close action is acceptable and stable, as the Modal component consistently exposes "Close" as the accessible label.

Learnt from: aditya-bansal-7
Repo: PalisadoesFoundation/talawa-admin PR: 2459
File: src/screens/UserPortal/People/People.test.tsx:226-242
Timestamp: 2024-11-24T19:35:45.258Z
Learning: In the `People` component, roles are not displayed in the table, so tests related to role display should account for this.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:155-157
Timestamp: 2025-04-20T07:34:29.946Z
Learning: The user prefers to structure tests by first checking if components render any elements at all (using general assertions), before proceeding to test specific content.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/screens/UserPortal/Organizations/Organizations.spec.tsx:19-19
Timestamp: 2025-01-26T12:32:45.867Z
Learning: In React test files, avoid using React hooks outside component scope (including in static objects like mock data). Instead, initialize hooks inside describe blocks or extract the needed functionality without using hooks.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/AddPeopleToTag/AddPeopleToTag.test.tsx:177-241
Timestamp: 2024-11-02T07:48:36.443Z
Learning: In `src/components/AddPeopleToTag/AddPeopleToTag.test.tsx`, prefer keeping test cases separate and more readable, even if it involves some duplication, instead of extracting common logic into helper functions.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3712
File: src/components/EventCalender/Yearly/YearlyEventCalender.spec.tsx:113-127
Timestamp: 2025-02-20T13:35:01.218Z
Learning: In React component tests, when testing window resize event handling, it's acceptable to only verify that the event is properly triggered without assertions if the test's focus is specifically on event handling rather than responsive behavior. Testing the actual responsive rendering would be a separate test case.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4040
File: cypress/pageObjects/AdminPortal/PeoplePage.ts:30-34
Timestamp: 2025-08-13T06:52:48.055Z
Learning: In the talawa-admin project's Cypress tests, specifically in cypress/pageObjects/AdminPortal/PeoplePage.ts, the element '[data-testid="existingUser"]' is a toggle control that requires .trigger('click') instead of .click() because it's not a standard button but a custom UI component that needs direct event triggering.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2397
File: src/screens/UserPortal/Volunteer/Actions/Actions.tsx:367-374
Timestamp: 2024-11-01T16:18:01.545Z
Learning: In the `src/screens/UserPortal/Volunteer/Actions/Actions.tsx` file, the search button intentionally includes `tabIndex={-1}`. This is acceptable for our application, and future reviews should not flag this as an accessibility concern.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4865
File: src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.spec.tsx:302-328
Timestamp: 2025-11-27T11:41:54.843Z
Learning: In Talawa Admin tests (e.g., src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.spec.tsx), using queryByLabelText with an HTMLElement cast for MUI Autocomplete inputs is acceptable because the Autocomplete input can mount asynchronously and isn't always available for strict getBy* queries at initial render. This pattern is stable for MUI Autocomplete components.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:367-0
Timestamp: 2024-11-02T07:32:43.099Z
Learning: In `src/components/TagActions/TagActions.tsx`, fragments around parentheses in the ancestor tags display are acceptable and should not be flagged as unnecessary.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.tsx:110-147
Timestamp: 2024-10-28T06:51:05.867Z
Learning: When handling the `useEffect` hooks for `addAncestorTagsData` and `removeAncestorTagsData` in `TagActions.tsx`, it's preferred to keep them separate to avoid confusion and enhance readability.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:229-252
Timestamp: 2024-06-30T21:44:02.495Z
Learning: When adding keyboard events for accessibility, consider potential user confusion and unintended navigations. Explore alternative approaches like tooltips or visual indicators to inform users about keyboard functionalities.

Learnt from: GlenDsza
Repo: PalisadoesFoundation/talawa-admin PR: 2064
File: src/screens/OrganizationFunds/OrganizationFunds.tsx:165-169
Timestamp: 2024-10-11T01:02:07.189Z
Learning: When suggesting adding keyboard events for accessibility, consider potential user confusion and explore alternative approaches like tooltips or visual indicators to balance accessibility and user experience.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagNode.tsx:129-137
Timestamp: 2024-10-28T08:21:01.364Z
Learning: When setting the aria-label for the checkbox in `TagNode.tsx`, it's acceptable to use `t('selectTag')` without including the tag name.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4760
File: src/utils/adminPluginInstaller.ts:256-260
Timestamp: 2025-11-23T12:02:06.471Z
Learning: In PalisadoesFoundation/talawa-admin, the CREATE_PLUGIN_MUTATION in src/utils/adminPluginInstaller.ts uses message string matching (checking for "already exists") to detect duplicate plugin errors because the backend doesn't currently expose structured error codes for this mutation. This is a known limitation that could be improved in the future with typed error responses from the API.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:216-0
Timestamp: 2024-11-02T07:31:50.788Z
Learning: In `src/components/TagActions/TagActions.tsx`, the submit button should not be disabled when no tags are selected, as per the design preference.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:251-274
Timestamp: 2024-10-28T06:33:09.726Z
Learning: In `TagActions.test.tsx`, negative test cases for tag operations can be deferred and added later if necessary, according to the team's plan.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2680
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:528-712
Timestamp: 2024-12-22T07:43:26.168Z
Learning: You prefer to keep migrated tests even if they appear duplicated because they originated from the old AdvertisementEntry.test.tsx file.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:123-131
Timestamp: 2024-10-28T06:38:43.765Z
Learning: In `TagActions.test.tsx`, `link2` is the error link used to simulate errors, so the existing test cases sufficiently cover error handling.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/screens/MemberDetail/MemberDetail.test.tsx:170-195
Timestamp: 2024-10-08T16:13:41.996Z
Learning: In unit tests for this project, direct `click()` calls are acceptable; avoid suggesting replacing them with `userEvent.click()`.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4077
File: package.json:189-213
Timestamp: 2025-08-17T07:39:34.255Z
Learning: The Talawa Admin codebase primarily uses .spec.tsx/.spec.ts naming convention for unit tests, with Cypress tests using .cy.ts pattern. However, there is at least one .test.tsx file in the codebase, so NYC exclude patterns should include both .spec and .test patterns.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 2482
File: src/components/AddOn/support/components/Action/Action.spec.tsx:1-8
Timestamp: 2024-11-27T06:37:47.871Z
Learning: In the Talawa-Admin project, the `testing-library/jest-dom` package is imported globally in `vitest.setup.ts`, so individual test files do not need to import it separately.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/EventManagement/EventRegistrant/EventRegistrants.tsx:16-19
Timestamp: 2025-02-13T01:55:19.334Z
Learning: PR #3577 has already refactored components to ensure no duplicate interfaces and proper type management for both the components and their children. This is part of the systematic refactoring approach being followed.

Learnt from: JaiPannu-IITI
Repo: PalisadoesFoundation/talawa-admin PR: 3592
File: src/components/UserPortal/ChatRoom/ChatRoom.tsx:23-23
Timestamp: 2025-02-14T21:04:11.392Z
Learning: The codebase is being refactored in alphabetical order, with components up to LoginPortalToggle already updated. Temporary type coexistence is maintained to prevent breaking changes until all related components are refactored.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-12T00:28:53.713Z
Learning: In talawa-admin PR #4565 continuation (PR #4664 planned), Phase 2A mock isolation strategy uses global vi.clearAllMocks() in afterEach (vitest.setup.ts) plus refactoring module-level vi.fn() into per-test beforeEach blocks across 6 parallelizable issues (2A.0 foundation, 2A.1-2A.4 directory-based fixes, 2A.5 validation). This approach addresses mock call history accumulation enabling maxConcurrency: 2 and 2.3-2.5x speedup. vi.restoreAllMocks() alternative considered for spy restoration during validation phase. Phase 2A (mocks) correctly separated from Phase 2B (DOM/Apollo).

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: Chaitanya1672
Repo: PalisadoesFoundation/talawa-admin PR: 2049
File: src/screens/OrganizationActionItems/ActionItemUpdateModal.tsx:112-138
Timestamp: 2024-10-08T16:13:41.996Z
Learning: The `istanbul ignore next` comments in the `ActionItemUpdateModal.tsx` file were added as part of a commit that introduced tests for the `ActionItemUpdateModal` component. Removing these comments and writing tests to cover the previously ignored lines is recommended to ensure code integrity and improve test coverage.

Learnt from: PurnenduMIshra129th
Repo: PalisadoesFoundation/talawa-admin PR: 3814
File: src/components/UserPortal/OrganizationNavbar/OrganizationNavbar.spec.tsx:137-146
Timestamp: 2025-03-11T17:45:54.621Z
Learning: In OrganizationNavbar.spec.tsx, separate vi.mock implementations for react-router-dom are needed to avoid errors - one for useNavigate and another for useParams.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:251-274
Timestamp: 2024-10-28T06:33:09.726Z
Learning: In `TagActions.test.tsx`, negative test cases for tag operations can be deferred and added later if necessary, according to the team's plan.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/AddPeopleToTag/AddPeopleToTag.test.tsx:177-241
Timestamp: 2024-11-02T07:48:36.443Z
Learning: In `src/components/AddPeopleToTag/AddPeopleToTag.test.tsx`, prefer keeping test cases separate and more readable, even if it involves some duplication, instead of extracting common logic into helper functions.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2680
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:528-712
Timestamp: 2024-12-22T07:43:26.168Z
Learning: You prefer to keep migrated tests even if they appear duplicated because they originated from the old AdvertisementEntry.test.tsx file.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts:0-0
Timestamp: 2025-10-22T22:00:53.943Z
Learning: In src/screens/OrganizationDashboard/OrganizationDashboardMocks.ts (and similar mock files), avoid duplicating identical Apollo MockedProvider mocks for repeated query consumption. Prefer adding `maxUsageCount` to the existing mock or using `newData` for reusable responses to keep tests deterministic and reduce drift.

Learnt from: bitbard3
Repo: PalisadoesFoundation/talawa-admin PR: 2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:145-155
Timestamp: 2024-12-02T04:20:11.745Z
Learning: In PRs focused solely on refactoring test cases from Jest to Vitest, avoid suggesting optimizations or changes outside the migration scope.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2362
File: src/components/TagActions/TagActions.test.tsx:123-131
Timestamp: 2024-10-28T06:38:43.765Z
Learning: In `TagActions.test.tsx`, `link2` is the error link used to simulate errors, so the existing test cases sufficiently cover error handling.

Learnt from: Jashan32
Repo: PalisadoesFoundation/talawa-admin PR: 4524
File: src/screens/Requests/Requests.spec.tsx:0-0
Timestamp: 2025-10-22T22:22:27.696Z
Learning: In talawa-admin tests using react-infinite-scroll-component (e.g., src/screens/Requests/Requests.spec.tsx), jsdom scroll is flaky. Prefer a resilient approach: try querying the container via document.querySelector('[data-testid="infinite-scroll-component"]') and fall back to window scroll if missing. Strengthen assertions by checking for page-2 items (e.g., "User9 Test") to ensure fetchMore actually ran instead of relying only on row counts.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/screens/MemberDetail/MemberDetail.test.tsx:170-195
Timestamp: 2024-10-08T16:13:41.996Z
Learning: In unit tests for this project, direct `click()` calls are acceptable; avoid suggesting replacing them with `userEvent.click()`.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4040
File: cypress/pageObjects/AdminPortal/PeoplePage.ts:30-34
Timestamp: 2025-08-13T06:52:48.055Z
Learning: In the talawa-admin project's Cypress tests, specifically in cypress/pageObjects/AdminPortal/PeoplePage.ts, the element '[data-testid="existingUser"]' is a toggle control that requires .trigger('click') instead of .click() because it's not a standard button but a custom UI component that needs direct event triggering.

Learnt from: bitbard3
Repo: PalisadoesFoundation/talawa-admin PR: 2588
File: src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx:155-162
Timestamp: 2024-12-03T05:52:37.888Z
Learning: In the `ChangeLanguageDropdown` component (`src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.tsx`), error handling has not been implemented. Therefore, test cases in `src/components/ChangeLanguageDropdown/ChangeLanguageDropdown.spec.tsx` do not cover error scenarios related to error handling.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:367-0
Timestamp: 2024-11-02T07:32:43.099Z
Learning: In `src/components/TagActions/TagActions.tsx`, fragments around parentheses in the ancestor tags display are acceptable and should not be flagged as unnecessary.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/screens/UserPortal/Organizations/Organizations.spec.tsx:19-19
Timestamp: 2025-01-26T12:32:45.867Z
Learning: In React test files, avoid using React hooks outside component scope (including in static objects like mock data). Instead, initialize hooks inside describe blocks or extract the needed functionality without using hooks.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4882
File: src/screens/UserPortal/Volunteer/UpcomingEvents/RecurringEventVolunteerModal.spec.tsx:69-109
Timestamp: 2025-11-28T16:02:31.790Z
Learning: In Talawa Admin test files (e.g., src/screens/UserPortal/Volunteer/UpcomingEvents/RecurringEventVolunteerModal.spec.tsx), developers prefer keeping date/time mocks (like vi.spyOn(Date.prototype, 'toLocaleDateString')) inline within individual test cases rather than consolidating them in beforeEach blocks, to maintain clarity and keep mocks close to the tests that use them, even if it results in some duplication.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-12T00:28:53.713Z
Learning: In talawa-admin PR #4565 continuation (PR #4664 planned), Phase 2A mock isolation strategy uses global vi.clearAllMocks() in afterEach (vitest.setup.ts) plus refactoring module-level vi.fn() into per-test beforeEach blocks across 6 parallelizable issues (2A.0 foundation, 2A.1-2A.4 directory-based fixes, 2A.5 validation). This approach addresses mock call history accumulation enabling maxConcurrency: 2 and 2.3-2.5x speedup. vi.restoreAllMocks() alternative considered for spy restoration during validation phase. Phase 2A (mocks) correctly separated from Phase 2B (DOM/Apollo).

Learnt from: NishantSinghhhhh
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/screens/UserPortal/UserScreen/UserScreen.spec.tsx:25-25
Timestamp: 2025-01-25T15:26:50.796Z
Learning: In test files, use the native localStorage API (localStorage.setItem/getItem) instead of React hooks for managing localStorage, as hooks can only be used within React components or custom hooks.

Learnt from: Doraemon012
Repo: PalisadoesFoundation/talawa-admin PR: 1988
File: src/components/LeftDrawerOrg/LeftDrawerOrg.test.tsx:282-282
Timestamp: 2024-09-29T06:51:31.295Z
Learning: In the test 'Component should be rendered properly' within 'Testing LeftDrawerOrg component for SUPERADMIN', setting 'SuperAdmin' to false is intentional.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2387
File: src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx:1-28
Timestamp: 2024-10-30T12:01:40.366Z
Learning: In the `MockAddPeopleToTag` component in `src/screens/ManageTag/ManageTagMockComponents/MockAddPeopleToTag.tsx`, it's acceptable to implement only the necessary props from `InterfaceAddPeopleToTagProps` and omit others like `refetchAssignedMembersData`, `t`, and `tCommon` that are tested separately.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/screens/OrganizationTags/OrganizationTags.test.tsx:184-0
Timestamp: 2024-11-02T07:18:39.563Z
Learning: In the `talawa-admin` project, it's acceptable for test cases in `src/screens/OrganizationTags/OrganizationTags.test.tsx` to test multiple behaviors within a single test function without needing to split them into smaller, focused tests.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 4077
File: package.json:189-213
Timestamp: 2025-08-17T07:39:34.255Z
Learning: The Talawa Admin codebase primarily uses .spec.tsx/.spec.ts naming convention for unit tests, with Cypress tests using .cy.ts pattern. However, there is at least one .test.tsx file in the codebase, so NYC exclude patterns should include both .spec and .test patterns.

Learnt from: rawadhossain
Repo: PalisadoesFoundation/talawa-admin PR: 4865
File: src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.spec.tsx:261-280
Timestamp: 2025-11-27T11:40:30.747Z
Learning: In Talawa Admin tests (e.g., src/components/EventRegistrantsModal/Modal/EventRegistrantsModal.spec.tsx), react-bootstrap Modal header close buttons don't support custom test IDs, so using getAllByRole('button', { name: /close/i })[0] to select the modal's primary close action is acceptable and stable, as the Modal component consistently exposes "Close" as the accessible label.

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-17T22:18:09.680Z
Learning: Talawa Admin Phase 2A testing guideline: Allow vi.hoisted() + vi.mock() module-level mocks for shared dependencies; prefer afterEach(() => vi.clearAllMocks()) as default cleanup. Use afterEach(() => vi.restoreAllMocks()) only in suites that create vi.spyOn spies or patch real implementations. Avoid vi.resetAllMocks() globally. The generic “no module-level mocks” rule is updated to “no module-level vi.fn except vi.hoisted module mocks.”

Learnt from: Ansingh0305
Repo: PalisadoesFoundation/talawa-admin PR: 0
File: :0-0
Timestamp: 2025-11-11T11:51:09.236Z
Learning: In talawa-admin PR #4664 (continuation of PR #4565 sharding work), global mock cleanup was implemented via vi.clearAllMocks() in vitest.setup.ts afterEach, along with Apollo Client warning suppression (temporary, pending follow-up PR) and test suite refactoring to per-test StaticMockLink instances. This test isolation strategy addresses mock state leakage that forced maxConcurrency: 1 in PR #4565, enabling future parallel test execution improvements and 3-4x speedup potential.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3526
File: src/setupTests.ts:35-36
Timestamp: 2025-02-02T14:28:38.521Z
Learning: In talawa-admin project, global timer setup using `vi.useFakeTimers()` and `vi.advanceTimersByTime(18000)` in `setupTests.ts` is the accepted approach for test files, as it works well with their test suite requirements.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 2482
File: src/components/AddOn/support/components/Action/Action.spec.tsx:1-8
Timestamp: 2024-11-27T06:37:47.871Z
Learning: In the Talawa-Admin project, the `testing-library/jest-dom` package is imported globally in `vitest.setup.ts`, so individual test files do not need to import it separately.

Learnt from: syedali237
Repo: PalisadoesFoundation/talawa-admin PR: 3712
File: src/components/EventCalender/Yearly/YearlyEventCalender.spec.tsx:113-127
Timestamp: 2025-02-20T13:35:01.218Z
Learning: In React component tests, when testing window resize event handling, it's acceptable to only verify that the event is properly triggered without assertions if the test's focus is specifically on event handling rather than responsive behavior. Testing the actual responsive rendering would be a separate test case.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 3400
File: src/components/SuperAdminScreen/SuperAdminScreen.spec.tsx:0-0
Timestamp: 2025-01-26T12:47:50.063Z
Learning: In the talawa-admin project, tests must use the custom `useLocalStorage` hook from 'utils/useLocalstorage' instead of the native localStorage API, as the test environment doesn't have direct access to browser's localStorage.

Learnt from: adithyanotfound
Repo: PalisadoesFoundation/talawa-admin PR: 3569
File: src/screens/UserPortal/Settings/Settings.spec.tsx:314-316
Timestamp: 2025-02-09T06:22:23.028Z
Learning: In the Settings component's tests, `fireEvent.change` should be used instead of `userEvent.type` for the address input field, as `userEvent` doesn't work correctly in this case.

Learnt from: bandhan-majumder
Repo: PalisadoesFoundation/talawa-admin PR: 3926
File: src/components/Advertisements/core/AdvertisementEntry/AdvertisementEntry.spec.tsx:155-157
Timestamp: 2025-04-20T07:34:29.946Z
Learning: The user prefers to structure tests by first checking if components render any elements at all (using general assertions), before proceeding to test specific content.

Learnt from: IITI-tushar
Repo: PalisadoesFoundation/talawa-admin PR: 2718
File: src/screens/UserPortal/Settings/Settings.spec.tsx:0-0
Timestamp: 2024-12-22T17:58:17.818Z
Learning: The matchMedia mock implementation in `Settings.spec.tsx` no longer includes the deprecated addListener and removeListener methods, opting solely for addEventListener and removeEventListener.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2398
File: src/components/TagActions/TagActions.tsx:216-0
Timestamp: 2024-11-02T07:31:50.788Z
Learning: In `src/components/TagActions/TagActions.tsx`, the submit button should not be disabled when no tags are selected, as per the design preference.

Learnt from: meetulr
Repo: PalisadoesFoundation/talawa-admin PR: 2425
File: src/screens/MemberDetail/MemberDetail.test.tsx:100-100
Timestamp: 2024-11-11T07:47:39.266Z
Learning: In `src/screens/MemberDetail/MemberDetail.test.tsx`, using `await wait();` is acceptable to wait for the render to complete.