-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set Up Testing for project #17
Closed
Closed
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
niyobern
force-pushed
the
ch-testing-setup
branch
from
June 6, 2024 21:08
f6680a9
to
58b3350
Compare
5 tasks
niyobern
force-pushed
the
ch-testing-setup
branch
from
June 6, 2024 21:34
58b3350
to
ac9250c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #17 +/- ##
========================================
Coverage 17.24% 17.24%
========================================
Files 4 4
Lines 29 29
Branches 4 4
========================================
Hits 5 5
Misses 21 21
Partials 3 3 ☔ View full report in Codecov by Sentry. |
niyobern
force-pushed
the
ch-testing-setup
branch
from
June 6, 2024 21:38
ac9250c
to
8eea2c2
Compare
niyobern
force-pushed
the
ch-testing-setup
branch
from
June 6, 2024 21:40
8eea2c2
to
ff6e724
Compare
13XAVI
approved these changes
Jun 7, 2024
niyobern
force-pushed
the
ch-testing-setup
branch
from
June 7, 2024 08:58
ff6e724
to
48e241f
Compare
jkarenzi
reviewed
Jun 7, 2024
jkarenzi
approved these changes
Jun 7, 2024
niyobern
force-pushed
the
ch-testing-setup
branch
from
June 7, 2024 09:51
48e241f
to
f0d4e68
Compare
jkarenzi
approved these changes
Jun 7, 2024
niyobern
added
the
Ready for TTL Review
the PR is ready to be reviewed by the TTL/Manager
label
Jun 7, 2024
dushimeemma
requested changes
Jun 7, 2024
niyobern
force-pushed
the
ch-testing-setup
branch
from
June 7, 2024 14:51
f0d4e68
to
5981922
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Description:
This PR introduces testing setup for our Vite + React + TypeScript project. The goal is to ensure that our components and business logic function as expected, and to catch any potential issues before they reach production.
Changes:
@testing-library/react
as dev dependencies.Test:
The test checks if the App component renders a paragraph with the text 'Welcome to Dynamites E-commerce'. This is done by rendering the App component and then using screen.getByRole('paragraph') to find the paragraph element. The toHaveTextContent assertion is then used to check if the paragraph contains the expected text.
Impact:
This change doesn't affect the existing functionality of the application but provides a foundation for writing more comprehensive tests in the future. This will help us ensure the quality and reliability of our application as we continue to develop and add new features.
How to Test:
After pulling the changes, run
npm run test
to test the App component