Basically we can use Travis to make sure each pull request into our develop and master branch is a working, build-able, and passing unit test before we actually merge them.
Maybe in future we can set up some coverage test to make sure we write unit test in each commit so our unit test is not falling behind.
https://github.com/integrations/codecov
adhikasp
commented
7 years ago
Travis is a tool for continuous integration. We should integrate it to our repo. https://github.com/integrations/travis-ci
Basically we can use Travis to make sure each pull request into our develop and master branch is a working, build-able, and passing unit test before we actually merge them.
Of course, Travis is worthless if we don't have any test in the first place. So this issue is blocked by https://github.com/blibli-future/detroit/issues/9 😄
Maybe in future we can set up some coverage test to make sure we write unit test in each commit so our unit test is not falling behind. https://github.com/integrations/codecov