test(DescriptionSection): add mock integration tests

[Robo-Synaptic-Vaish]

Fixes #6939

Note

While working on this test, I noticed that DescriptionSection.tsx currently does not include any asynchronous service calls, cache handling, database retrieval, or loading states.

So instead of adding mocks for functionality that is not present in the component, the tests focus on the integrations that actually exist:

• Mocking SectionCard and FieldLabel for isolated testing
• Verifying component rendering and prop flow
• Testing onChange behavior and character limit handling
• Ensuring the component remains stable during updates

This keeps the test coverage aligned with the current implementation of DescriptionSection.

Pillar

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

Visual Preview

N/A (Test-changes only).

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[github-actions]

🚨 Hey @Robo-Synaptic-Vaish, 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. 💪

[Aamod007]

Excellent implementation of mock integration tests for the DescriptionSection component. Testing the input constraints and field label interactions ensures a stable component behavior. However, this PR is blocked by a failing CI check. Please resolve the issues and rerun the CI pipeline.

[github-actions]

⚠️ Hey @Robo-Synaptic-Vaish, this pull request has been inactive for 3 days. It will be automatically closed in 2 days if no further activity occurs.

If you are still working on this, please push your latest changes or leave a comment to keep it active.