-
Notifications
You must be signed in to change notification settings - Fork 45
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
Expand test coverage for utils/parser.js #197
Comments
Hello, |
@barrotsteindev awesome! Let me know if you have questions or need a hand with anything |
Well I have looked into it and it seems like this issue is no longer relevant. |
@barrotsteindev It looks like the coverage is still about 93% with a couple of error states that are untested. Specifically lines 60 and 84 are not executed in the test suite. If you wanted to write some tests to get them under coverage that would be great. There might need to be some refactoring to make that a little easier to do... but I think it is possible as is with some correct setup of the params passed into the function |
@designfrontier |
Hi @designfrontier I am located in India (IST) Hoping for a response soon !!! |
https://coveralls.io/builds/4658528 Looks like it is covered about 90%...
Locally you can get this number by running
npm test
. That creates an output to console and the more useful coverage directory. In the coverage directory (run it with a static server likehttp-server
) you can drill into the coverage in the browser and see exactly what lines are not tested currently.The text was updated successfully, but these errors were encountered: