Running unit tests on a continuous integration service like Travis CI or Wercker
This is the last article in a series of three in which I explain how I setup my JavaScript unit testing with code coverage and getting it to run on a CI Server. First I described how to add unit testing and then I showed how to configure Istanbul and Grunt to generate code coverage reports. In this third step I will explain how I configured the project to use a continuous integration (CI) server like Travis CI or Wercker to run the unit tests when changes are pushed to the Git server.