Skip to content

Latest commit

 

History

History
49 lines (35 loc) · 1.61 KB

3.md

File metadata and controls

49 lines (35 loc) · 1.61 KB

Step 3: See your progress - Travis CI and Coveralls

In this step, you will commit your changes, and create a pull request. This will kick off continuous integration and coverage reporting, which you can see from your pull request.

  1. Take a look at:

You can see that the build is successfully passing, but the overall coverage is pretty low.

  1. Commit your new unit tests from Step 2 to your fork of catinabox (you can create a separate branch if you'd prefer):
christie@paw-paw:~$ git add -u
christie@paw-paw:~$ git diff --cached
christie@paw-paw:~$ git commit
  1. When you are happy with your commit and your changes, push them back to your fork:
christie@paw-paw:~$ git push origin master

  1. Visit github and open a new pull request:

  2. [https://github.com/keeppythonweird/catinabox]

  3. 'Open Pull Request' or 'Pull Requests' -> 'New Pull Request'

  4. As soon as the pull request is created, you will see three checks run:

  5. Travis CI - Running all tests for python 2.7

  6. Travis CI - Running all tests for python 3.4

  7. Coveralls measuring the test coverage for your branch

  8. If you see a build failure, you can run all tests locally:

christie@paw-paw:~$ python setup.py test

However if the failure is with the other major version of python (e.g. you are running 3.4 locally but the 2.7 build broke) you will not be able to reproduce the failure.