We should use Coveralls! It's shiny. If we have Travis already, we can just add that to the repo with minimal effort.
Advantages: Gives us a decent idea of what's "covered" by tests, what's not. This is big, because this project is big. If we have full coverage, we'll have a much fuller test suite. This will also encourage me to finish the test suite.
Disadvantages: Another shiny service! How distracting.
Functionally, this will only involve adding a couple of lines and a configuration file, as well as setting some environment variables in Travis. I can handle this all.
We should use Coveralls! It's shiny. If we have Travis already, we can just add that to the repo with minimal effort.
Advantages: Gives us a decent idea of what's "covered" by tests, what's not. This is big, because this project is big. If we have full coverage, we'll have a much fuller test suite. This will also encourage me to finish the test suite.
Disadvantages: Another shiny service! How distracting.
Functionally, this will only involve adding a couple of lines and a configuration file, as well as setting some environment variables in Travis. I can handle this all.