Skip to content

test(CustomizeCTA): add timezone boundary test coverage#8088

Open
Shikhartiwari967 wants to merge 1 commit into
JhaSourav07:mainfrom
Shikhartiwari967:test-customizecta-timezone-boundaries
Open

test(CustomizeCTA): add timezone boundary test coverage#8088
Shikhartiwari967 wants to merge 1 commit into
JhaSourav07:mainfrom
Shikhartiwari967:test-customizecta-timezone-boundaries

Conversation

@Shikhartiwari967

Copy link
Copy Markdown
Contributor

Description

Fixes #6825

Added a new test suite for CustomizeCTA to verify timezone normalization and calendar data boundary behavior.

Changes

  • Added CustomizeCTA.timezone-boundaries.test.tsx
  • Mocked multiple timezone environments (UTC, IST, EST, JST)
  • Verified consistent component rendering across different timezones
  • Ensured timezone changes do not affect component stability
  • Added 5 isolated Vitest test cases

Pillar

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

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.
  • This PR only adds automated test coverage.
  • The new test suite passes locally (5/5 tests).

Notes

npm run typecheck currently reports existing repository-wide TypeScript issues (e.g. lib/rss.ts and app/generator/components/*) that are unrelated to this test-only change.

@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

Copy link
Copy Markdown
Contributor Author

Hi @Aamod007 sir,

The new CustomizeCTA.timezone-boundaries.test.tsx test suite passes locally (5/5 tests), and the component-specific tests run successfully.

The current CI failure appears to come 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 timezone boundary test coverage for CustomizeCTA.

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

@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-timezone-boundaries): verify Timezone Normalization & Calendar Data Boundary Alignment (Variation 8)

1 participant