Skip to content

test(CustomizeCTA): add responsive breakpoint test coverage#8086

Open
Shikhartiwari967 wants to merge 1 commit into
JhaSourav07:mainfrom
Shikhartiwari967:test-customizecta-responsive-breakpoints
Open

test(CustomizeCTA): add responsive breakpoint test coverage#8086
Shikhartiwari967 wants to merge 1 commit into
JhaSourav07:mainfrom
Shikhartiwari967:test-customizecta-responsive-breakpoints

Conversation

@Shikhartiwari967

Copy link
Copy Markdown
Contributor

Description

Fixes #6824

Added a new responsive breakpoint test suite for the CustomizeCTA component.

The test suite verifies:

  • Responsive flex layout classes
  • Responsive heading typography
  • CTA link accessibility
  • Responsive spacing utilities
  • Successful rendering

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-only change)

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 commits follow the Conventional Commits format.
  • I have updated README.md if required.
  • I have starred the repository.
  • I have made sure I have only one commit in this PR.
  • The change only adds test coverage.
  • I joined the CommitPulse Discord community.

@vercel

vercel Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

@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.

@github-actions github-actions Bot added the status:blocked This PR is blocked due to a failing CI check. label Jul 15, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🚨 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

Shikhartiwari967 commented Jul 15, 2026

Copy link
Copy Markdown
Contributor Author

Hi! @Aamod007 Sir, I verified the CI failure locally by running npm run typecheck on the latest main branch.

The reported TypeScript errors are in:

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

This PR only adds app/components/CustomizeCTA.responsive-breakpoints.test.tsx, and the new test passes locally. Please let me know if you'd like me to make any changes to this PR.

@Shikhartiwari967

Copy link
Copy Markdown
Contributor Author

Hi @Aamod007 sir , please review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status:blocked This PR is blocked due to a failing CI check.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

test(CustomizeCTA-responsive-breakpoints): verify Responsive Multi-device Columns & Mobile Viewport Layouts (Variation 7)

1 participant