Travis-CI does not support multiple languages, and so we can only test a single version of each language (and then, only if it happens to be installed in the default Travis images). We could hack Travis to install the things we want manually, but that is too much of a hack for my tastes.
Instead, let's create a set of tests using Vagrant. This way, anyone can run them on their own systems, and we can work/debug locally. We lose the automation Travis gives us, but this is a small repository, with infrequent commits, so we don't need a full CI system. We'll just manually enforce the policy that we have to test before we commit or accept a pull request.
Travis-CI does not support multiple languages, and so we can only test a single version of each language (and then, only if it happens to be installed in the default Travis images). We could hack Travis to install the things we want manually, but that is too much of a hack for my tastes.
Instead, let's create a set of tests using Vagrant. This way, anyone can run them on their own systems, and we can work/debug locally. We lose the automation Travis gives us, but this is a small repository, with infrequent commits, so we don't need a full CI system. We'll just manually enforce the policy that we have to test before we commit or accept a pull request.