-
Notifications
You must be signed in to change notification settings - Fork 1
attempting to add coveralls to Repo #16
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
Conversation
|
Builds are in stuck in Travis queue for a long time. Not sure if this is a problem with the .yml file or if it's just because it's a Monday morning and a bunch of builds are starting at the same time. |
|
Build now passes and report displays |
jackblanc
left a comment
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.
LGTM
|
|
||
| describe('Request Interceptor Tests', () => { | ||
| /* | ||
| it('properly applies the access token when one exists in storage', () => { |
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.
Was this test not passing?
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.
Yeah this test was failing
|
@jackblanc Merged with updated master which has some script changes, mind giving this another quick review before this gets merged into master? |
Why
Monday.com Ticket
What benefit does this bring to the end user? Or, what benefit does this bring to developers working in the codebase?
Adds coveralls to the frontend which allows us to check the coverage of our test suite
This PR
Describe the changes required and any implementation choices you made to give context to reviewers.
Added the node coveralls library and added a new script for coveralls to package.json
Screenshots
Provide screenshots of any new components, styling changes, or pages.
Verification Steps
What steps did you take to verify your changes work? These should be clear enough for someone to be able to clone the branch and follow the steps themselves.
I am checking travis builds and looking at the coveralls page:
https://coveralls.io/github/Code-4-Community/frontend-scaffold