Test/UI hero section responsive#1800
Conversation
|
@amna-sehgal 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 @amna-sehgal, 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 |
Aamod007
left a comment
There was a problem hiding this comment.
Unapproving — this PR has the \status:blocked\ label. Please resolve the blocking issue and re-request review.
Aamod007
left a comment
There was a problem hiding this comment.
This PR has the \status:blocked\ label. Please resolve the blocking issue first.
Aamod007
left a comment
There was a problem hiding this comment.
Unapproving — this PR has a
eeds-rebase\ or \status:blocked\ label. Please resolve that first and re-request review.
Description
Fixes #1527
This PR adds and finalizes unit tests for the HeroSection (Variation 2) component. It verifies that the component renders correctly, including the main heading and supporting text content, and ensures stable rendering across simulated mobile and tablet viewport conditions.
All previous test failures related to incorrect visibility matchers and unsupported assertions have been resolved in compliance with React Testing Library best practices.
Pillar
Visual Preview
Not applicable (unit test changes only)
Checklist before requesting a review:
CONTRIBUTING.mdfile.npx vitest run)npm run formatandnpm run lintlocally and resolved all errors (CI will fail otherwise).test(ui): ...).README.mdif required.