Wouldn't it be convenient if someone else was in charge of running all our tests every time we made a change to our code base? This would mean that we couldn't forget to run some specific tests just because they were related to an area of the code that we were not directly touching.
That's exactly the goal of Continuous Integration (CI) environments. Every time we push our changes to the code repository, these environments will notice and rerun the tests, usually merging our changes with the changes from our colleagues to make sure they cope well together.
If you have a code repository on GitHub, using Travis as your CI is a fairly straightforward process. Suppose that I made an amol-/travistest GitHub project where I pushed the code base of our chat application; to enable Travis, the first thing that I have to do is to go to https://travis-ci.com/ and log in with my GitHub credentials:
Once we...
