Added .travis.yml

[refi64]

Take 1! (I probably did at least one thing wrong, but I guess I'll find out...)

[mvcisback]

I might be missing something, but why not just use:
nosetests tests.py lib-typing/3.2/test_typing.py mypy/test

Or something like make test (where the make files test rule is the above)

[JukkaL]

@kirbyfan64 Just a few quick notes: How do you report errors to the CI systen? What if a single step fails, would you still run the others? The script should live in a subdirectory, I think.

@mvcisback The tests use a custom test framework (Iong story...) and nose won't work. However, migrating to unittest + nose/pytest would make sense. See #381 and #380.

[mvcisback]

@JukkaL nosetests should run any function that has the word test in it....the integration with unittest and such is optional

[refi64]

@JukkaL Travis maintains a log of all the output of the commands. If a single step fails, the others do run, largely so you can still see the other tests, too. If you want me to use a Makefile though, I'll do so.

[JukkaL]

How does Travis know if any of the steps in the shell script fails? Does it track the exit statuses of the commands somehow? Or does it look at the stdout/stderr output?

[refi64]

@JukkaL I just fixed that.

[JukkaL]

@mvcisback The mypy unit test framework uses some conventions that are incompatible with nose.