Increasing Access

easier for contributors and community as a whole to understand test files and maintain consistency throughout the project in test naming conventions. It would allow new contributors to adopt the good naming convention from day one as mentioned in the docs.

Feature enhancement details

renaming all the test files which don't specify if they are unit or integration, correctly specifying their type in the file name.

i.e someComponentName.test.ts -> someComponentName.unit.test.ts

Test files with wrong naming convention

I have list down all the test files in the client folder which don't specify their type of test and their correct type in the brackets in front:

• (unit) client/common/Button.test.tsx - Reusable user-facing button variants (button, internal link, external link).
• (unit) client/common/ButtonOrLink.test.tsx - Reusable primitive that conditionally renders button/link and handles click/navigation behavior.
• (unit) client/common/IconButton.test.tsx - Reusable icon button behavior/props checks.
• (unit) client/common/RouterTab.test.tsx - Reusable tab link component behavior and router path change assertion.
• (unit) client/common/Tooltip.test.tsx - Reusable tooltip interaction states (hover/focus/visibility).
• (unit) client/common/useKeyDownHandlers.test.tsx - Hook-level keyboard handler behavior in isolation.
• (unit) client/common/useModalClose.test.tsx - Hook-level modal close behavior in isolation.
• (unit) client/common/usePrevious.test.tsx - Hook-level state transition behavior in isolation.
• (unit) client/common/useSyncFormTranslations.test.tsx - Hook-level form translation sync behavior in isolation.

• (unit) client/components/Dropdown/DropdownMenu.test.tsx - Reusable dropdown component behavior (open/select/close).
• (unit) client/components/Menubar/Menubar.test.tsx - Reusable menubar system behavior (keyboard, submenu, ARIA).
• (unit) client/components/PreviewNav.test.tsx - User-facing nav component rendering/interaction checks.
• (unit) client/components/SkipLink.test.tsx - User-facing accessibility control behavior.

• (unit) client/utils/consoleUtils.test.ts - Utility function outputs for parsing/offset logic.
• (unit) client/utils/device.test.ts - Utility function behavior for platform detection conditions.
• (unit) client/utils/dispatcher.test.ts - Utility module behavior (registerFrame, dispatchMessage, listeners).
• (unit) client/utils/evaluateExpression.test.ts - Utility function behavior and error handling in isolation.
• (unit) client/utils/formatDate.test.ts - Utility formatting behavior over controlled date inputs.
• (unit) client/utils/getConfig.test.ts - Utility config resolution behavior by environment shape.
• (unit) client/utils/language-utils.test.ts - Utility language resolution behavior from navigator inputs.
• (unit) client/utils/parseStringToType.test.ts - Utility parsing behavior for number/boolean conversion paths.
• (unit) client/utils/parseURLParams.test.ts - Utility URL parsing behavior over query param permutations.
• (unit) client/utils/reduxFormUtils.test.ts - Validation utility behavior for form input variants.

@raclim @clairep94 @ksen0

Thanks a lot for your time.