test : Improve Test Coverage for UI Components

## Issue Summary

Add Unit Tests for Core UI Components (Pavani - Components Module)

This issue focuses on creating unit test coverage for key reusable UI components in the application. Currently, these components lack proper test coverage, which may lead to undetected UI bugs and reduced code reliability.

---

## Problem Statement

• Several core UI components do not have unit tests implemented
• Lack of test coverage increases risk of UI regressions
• Components are reused across pages, so failures impact multiple features
• Difficult to validate rendering, props handling, and interactions

Affected Users:

• Developers (harder debugging and maintenance)
• End users (potential UI inconsistencies)

---

## Proposed Solution

• Create unit test files for each component under:
  src/__tests__/components/
• Follow existing patterns from:
  • Hero.test.tsx
  • Footer.test.tsx
• Cover:
  • Rendering behavior
  • Props validation
  • User interactions

---

## Test-Driven Development

Acceptance Criteria (Given-When-Then)

Scenario 1: Component renders correctly

Given the component is loaded When it is rendered Then it should display all required UI elements

Scenario 2: Component receives props

Given valid props are passed When the component renders Then it should display data correctly based on props

Scenario 3: User interaction works

Given the component has interactive elements When the user performs an action (click/scroll) Then the expected behavior should occur

---

## Test Cases

Test ID	Test Description	Precondition	Test Steps	Expected Result	Priority
TC-001	Render component	Component available	1. Import2. Render	UI renders without crash	High
TC-002	Props handling	Props passed	1. Pass props2. Render	Correct data displayed	High
TC-003	Interaction test	Interactive component	1. Trigger event2. Observe	Expected action triggered	Medium

---

## Unit Test Requirements

Components to Test

Component	Test Focus
Navbar.tsx	Navigation rendering, links
ProjectCard.tsx	Props display, UI structure
ProjectList.tsx	List rendering
ProjectSummaryCard.tsx	Data rendering
ScrollToTop.tsx	Scroll behavior
SummerCard.tsx	UI + props

---

Test Assertions Required

• Renders correctly with initial state
  • Handles props correctly
  • Displays dynamic content
  • Handles user interactions
  • No runtime errors

---

## Implementation Details

Files to Change

File Path	Action	Purpose
src/__tests__/components/Navbar.test.tsx	Create	Test Navbar
src/__tests__/components/ProjectCard.test.tsx	Create	Test ProjectCard
src/__tests__/components/ProjectList.test.tsx	Create	Test ProjectList
src/__tests__/components/ProjectSummaryCard.test.tsx	Create	Test Summary Card
src/__tests__/components/ScrollToTop.test.tsx	Create	Test Scroll behavior
src/__tests__/components/SummerCard.test.tsx	Create	Test SummerCard

---

## Technical Considerations

• Use Jest + React Testing Library
• Follow existing test structure
• Use mock data for props
• Keep tests isolated and reusable

---

## UI/UX Requirements

• Components should render correctly across screen sizes
• Ensure accessibility (basic checks like text visibility)
• Verify interactive elements (buttons, scroll, links)

---

## Testing Strategy

Manual Testing

1. Render components in UI
2. Verify layout and content
3. Check interactions (click, scroll)

---

Automated Testing

• Component render tests
  • Props validation tests
  • Interaction tests

---

## Test Data Requirements

const mockProps = { title: "Sample Project", description: "Test description", };

---

## Definition of Done

• All components have test files
  • Tests pass successfully
  • Minimum coverage achieved
  • Code reviewed
  • No console errors
  • Lint checks passed

---

## Additional Context

Related Issues

• Related to overall test coverage improvement

Notes

• Follow same structure as existing test files
• Ensure consistency across all component tests

---