-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feat/join a ride #48
Feat/join a ride #48
Conversation
lupyana
commented
May 25, 2019
- Create api end point and test case for joining a ride see Request to join a ride #43
- Added coveralls to project Integrate coveralls #47
- Updated readme file
…o feat/join-a-ride
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.
@lupyana Coverage files ain't them generated on running tests?
If you mean the coverage folder, it is auto generated after running tests |
So what happens if tests are executed in travis? |
Travis will build and perform the unit and coverage tests, After is is complete coverals will read the repo, to get results of the coverage test.It will prepare a report showing which parts of the code wasn’t covered by the test suites |
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.
ok @lupyana but I agree with @makoscafee from what I know coverage files are not committed in repos. I think @makoscafee have explained it well there |
Yes noted, however it is already in my gitignore file. I have to find anotherway to remove it from the remote repo |
@makoscafee I have removed the coverage folder |
LGTM you can merge. |