feat (test): write unit tests for Footer #249
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
JimmyTron
approved these changes
Sep 24, 2024
sonylomo
approved these changes
Oct 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Have you read the contributing guidelines ?
What is the purpose of your pull request?
Proposed changes
Unitande2eTests to Footer Component #240 by creating unit tests for Footer component usingvitest. I already added E2E tests for the Footer in Fix footer spacing issues #223 usingplaywright.playwright.config.cjsto only run e2e tests on test files ending in.spec.jsWarning
Please read these points carefully and answer honestly with an
Xinto all the boxes. Example : [X]
Before submitting a pull request make sure you have:
How to Check and Fix Linting Issues
Run
npm run validate. This command will run prettier and eslint checks to ensure linting guidelines are respected.If the command exits with code 0 (build is successful), there are no linting issues.
If the command exits with a code other than 0, scroll up the command output and look for identified linting issues. Fix them and revalidate to check if the issues have been resolved by re-running the command.