-
-
Notifications
You must be signed in to change notification settings - Fork 23
Test/unit/utils #67
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
base: master
Are you sure you want to change the base?
Test/unit/utils #67
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Looks clean. Let me test |
|
To run the test cd in the test directory and run npm run test:unit |
|
i am extremely sorry, I didn't opened my system today |
|
@JP-sDEV I am working on some patches i will merge it after making some changes |
|
Many tests are failing almost every @JP-sDEV But it shouldn't all expected tests are not as per format. HTTP format is not like just simple text. Make it at least pass 80% |
|
@IntegerAlex sure, I will revise the tests to match the project specs. What content-types are supported? Also is |
|
Okay i will fix Query parser |
testdirectory to include unit tests - allows for flexibility (e.g. include integration tests in the future)npm run unit:testto run all unit testslib/utils.jsSuggestion: combine
test/package.jsonwithpackage.json(i.e. found in the root), to simplify the scripts and requirements. This also allows for jest to analyze test coverage.