-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
test: Tests for colorPreference and getUserPRVelocity #190
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this. 👍👍
The failing test is passing in my local dev environment. |
Same with me. |
Weird 😕, can you try changing the test just a bit so the value changes to something else? It passes for me too. |
Sure, will revert back |
This could be due to the varying timezone of the test runner. The Edit: This shouldn't be a problem since we're getting the difference in days of 2 dates of the same timezone. |
So should I try changing the time zone in the tests? |
Can you try using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Compliance Checks
Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.
Issue Reference
In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide.
This check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.
Watched Files
This pull request modifies specific files that require careful review by the maintainers.
Files Matched
- npm-shrinkwrap.json
- package.json
Why did changing it to Math.floor work? |
I suggested Now that the tests pass, there are a few linting errors at https://github.com/open-sauced/ai/actions/runs/5325886058/jobs/9647205001?pr=190. Once they are resolved, we can get this merged. |
## [1.8.1-beta.1](v1.8.0...v1.8.1-beta.1) (2023-06-20) ### ✅ Tests * Tests for colorPreference and getUserPRVelocity ([#190](#190)) ([6b9a5c3](6b9a5c3))
🎉 This PR is included in version 1.8.1-beta.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
## [1.9.0](v1.8.0...v1.9.0) (2023-06-29) ### ✅ Tests * Tests for colorPreference and getUserPRVelocity ([#190](#190)) ([6b9a5c3](6b9a5c3)) ### 🍕 Features * post to linkedin projects ([#177](#177)) ([a20bff4](a20bff4)) ### 🐛 Bug Fixes * Made the "Tools:" conditional according to the current page ([#197](#197)) ([b08ad07](b08ad07)), closes [issue#112](https://github.com/open-sauced/issue/issues/112) [issue#112](https://github.com/open-sauced/issue/issues/112) * separate vite and vitest configs ([#193](#193)) ([7a980c8](7a980c8))
🎉 This PR is included in version 1.9.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
## [1.8.1-beta.1](open-sauced/ai@v1.8.0...v1.8.1-beta.1) (2023-06-20) ### ✅ Tests * Tests for colorPreference and getUserPRVelocity ([#190](open-sauced/ai#190)) ([6b9a5c3](open-sauced/ai@6b9a5c3))
## [1.9.0](open-sauced/ai@v1.8.0...v1.9.0) (2023-06-29) ### ✅ Tests * Tests for colorPreference and getUserPRVelocity ([#190](open-sauced/ai#190)) ([6b9a5c3](open-sauced/ai@6b9a5c3)) ### 🍕 Features * post to linkedin projects ([#177](open-sauced/ai#177)) ([a20bff4](open-sauced/ai@a20bff4)) ### 🐛 Bug Fixes * Made the "Tools:" conditional according to the current page ([#197](open-sauced/ai#197)) ([b08ad07](open-sauced/ai@b08ad07)), closes [issue#112](https://github.com/open-sauced/issue/issues/112) [issue#112](https://github.com/open-sauced/issue/issues/112) * separate vite and vitest configs ([#193](open-sauced/ai#193)) ([7a980c8](open-sauced/ai@7a980c8))
What type of PR is this? (check all applicable)
Description
This PR is related to Write tests for utility functions #188 and adds tests for the following files:
In order to work with window object, modifications were made to the Vite config, setting the environment to 'jsdom',
No other files or tests were changed or affected.
Related Tickets & Documents
[#188]
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?