Add Mock Integration Test Coverage for CustomizeCTA Component

[Shikhartiwari967]

Description

Fixes #6826

Added a dedicated test suite for CustomizeCTA to verify asynchronous service layer mocking and integration behavior.

Changes

• Added CustomizeCTA.mock-integrations.test.tsx
• Mocked Next.js Link integration
• Mocked TranslationContext
• Mocked Framer Motion
• Verified component renders correctly using mocked integrations
• Added five isolated Vitest test cases

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Testing)

Visual Preview

N/A (Test-only changes)

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally.
• I have run npm run lint locally.
• My commit follows the Conventional Commits format.
• I have updated README.md if required (not applicable).
• I have starred the repository.
• I have made sure that I have only one commit in this PR.
• The new test suite passes locally.

Notes

Repository-wide typecheck failures, if any, originate from unrelated existing files outside the scope of this PR.

[vercel]

@Shikhartiwari967 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[retenta-bot]

This PR introduces a new test suite for the CustomizeCTA component, which enhances our testing coverage by mocking various integrations. This approach is similar to previous decisions made for other components, such as the SuccessGuide and CommitPulseSection, where we emphasized the importance of testing under different scenarios without relying on real network calls. It's great to see this focus on robust testing practices! Looking forward to your feedback.

[github-actions]

🚨 Hey @Shikhartiwari967, 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. 💪

[Shikhartiwari967]

Hi @Aamod007 Sir,

The new CustomizeCTA.mock-integrations.test.tsx test suite passes locally and the component-specific tests complete successfully.

The current CI failure appears to originate from existing repository-wide TypeScript issues in:

app/generator/components/EditorPanel.type-compiler.test.tsx
app/generator/components/PreviewPanel.type-compiler.test.tsx

These files are outside the scope of this PR, which only adds mock integration test coverage for CustomizeCTA.

Please let me know if any changes are required from my side. Thank you!