All developers should know the value in unit testing and automated builds. They ensure quality is built and maintained in your software products. You don’t want to have you interns come in and add some cool functionality into your product and deploy a broken product because they didn’t understand how their changes impacted existing functionality. In my last post in this series I went over how to create unit tests for a node.js application. Unit tests by themselves are great, but you (and your intern) need to execute them for there to be any value in having them. Chances are that intern doesn’t know about unit testing and won’t know they should, or even how to, run the unit tests before committing their changes. Fortunately there are tools that automate testing and reporting on commits. Travis is one such tool, and it is free to use. Setting it up for my node application was stupid easy. There were three steps, first I needed to define a “default” gulp task like so:
This step is necessary because I only defined the “run-test” task in gulp when setting up the unit tests, Travis by default runs the “default” gulp task, so it needs to exist. Second you need to create a “.travis.yml” file to define how Travis should run.
Third, you need to log in to Travis with your github account and select the repository to test. That is it. You are then running and testing automatically. If all is setup up right you will see a screen like this shortly after pushing your changes to github, complete with your “build passing” badge. Awesome!