Menu
We would like to improve our code quality, but we’re working on legacy code and using Travis-CI now would trigger lots of changes that the team won’t be able to handle.
To improve code step by step, I was wondering if there is a way to check only modified files, or even better: just the modified lines.
We could get rid of inconsistencies as we code and switch to “all code coverage” once we feel we have the time for it.
744
Configuration. Travis CI is configured by adding a file named . travis. yml , which is a YAML format text file, to the root directory of the repository.
Coveralls is a hosted analysis tool, providing statistics about your code coverage. Configuring your Travis CI build to send results to Coveralls always follows the same pattern: Add your repository to Coveralls.
To speed up a test suite, you can break it up into several parts using Travis CI's build matrix feature. Say you want to split up your unit tests and your integration tests into two different build jobs. They'll run in parallel and fully utilize the available build capacity for your account.
Travis-CI runs on a Git repository with the code checked-out. You can teach your test scripts to run git diff --name-only HEAD^ to get the modified files, and then run only the tests corresponding to them.
93
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
