Split integration tests in Travis into separate jobs (#100)
Split integration tests in Travis into separate jobs (#100)

* Split integration tests in Travis into separate jobs

Not so much trying to speed things up as to provide better visibility
into failures at a glance.

Note that this changes the `script` that Travis will run from `setup.py
test` to `setup.py nosetests` ... not sure if there was an explicit
desire to AVOID using nose in this context, but I WANT to use nose in
order to use the same `-A integration!=X` flag that is illustrated in
the gapipy README:
    https://github.com/gadventures/gapipy#testing

oh, neat, that's a python expression:
    https://nose.readthedocs.io/en/latest/man.html#cmdoption-eval-attr

gadventures/gapipy