test(CustomizeCTA): add timezone boundary test coverage#8088
test(CustomizeCTA): add timezone boundary test coverage#8088Shikhartiwari967 wants to merge 1 commit into
Conversation
|
@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. |
|
🚨 Hey @Shikhartiwari967, the CI Pipeline is failing on this PR and it has been marked as 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 passes2. Auto-fix common issues: npm run format # Auto-fix formatting with Prettier
npm run lint -- --fix # Auto-fix lint errors where possible3. Check the full failure log here: Once you push a fix and the CI passes, the |
|
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 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! |
|
Hi @Aamod007 sir, please review it. |
Description
Fixes #6825
Added a new test suite for
CustomizeCTAto verify timezone normalization and calendar data boundary behavior.Changes
CustomizeCTA.timezone-boundaries.test.tsxPillar
Visual Preview
N/A (Test-only changes)
Checklist before requesting a review:
CONTRIBUTING.mdfile.npm run lintlocally.README.mdif required (not applicable).5/5tests).Notes
npm run typecheckcurrently reports existing repository-wide TypeScript issues (e.g.lib/rss.tsandapp/generator/components/*) that are unrelated to this test-only change.