test(useRecentSearches-accessibility): verify Accessibility Standards & Screen Reader Aria Compliance (Variation 4)

[pari-dubey1]

Description

Fixes #4620

Introduces a robust unit test suite for the useRecentSearches.ts custom hook. Since the target file is a state hook rather than a visual layout component, traditional DOM accessibility nodes (such as ARIA attributes, landmarks, and tab indexing configurations) are inherently handled by consuming parent wrappers rather than the hook itself.

To provide high-value code coverage, this test module explicitly isolates and verifies the hook's true functional behaviors, including:

• Pre-populating historical states via loadFromStorage() on hydration.
• Triggering state serialization out to writeStorage() under localStorage.
• Shuffling duplicate entry sequences to the absolute front of the stack (index 0).
• Guarding against whitespace-only or empty query string appending loops.
• Targeted item isolation eviction via removeSearch().

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs, hooks logic testing)

Visual Preview

(N/A: Automated logical unit testing coverage expansion).

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally.
• I have run npm run format and npm run lint locally and resolved all errors.
• My commits follow the Conventional Commits format (test(useRecentSearches-accessibility): ...).
• I have made sure that I have only one commit to merge in this PR.

[github-actions]

🚨 Hey @pari-dubey1, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪