26 | | cp ../variant/README.md ./ # Copying README.md from Boost.Variant |
27 | | sed -i 's/variant/lexical_cast/g' README.md # Replacing `variant` with `lexical_cast` |
28 | | sed -i 's/apolukhin/<your_login>/g' README.md # Replace `apolukhin` login name wuth your own login name |
29 | | gedit README.md # ... editing README.md in editor |
30 | | git add README.md # Adding README.md for next commit |
| 29 | cp ../variant/README.md ./ # Copying README.md from Boost.Variant |
| 30 | sed -i 's/variant/lexical_cast/g' README.md # Replacing `variant` with `lexical_cast` |
| 31 | sed -i 's/apolukhin/<your_login>/g' README.md # Replace `apolukhin` login name wuth your own login name |
| 32 | gedit README.md # ... editing README.md in editor |
| 33 | git add README.md # Adding README.md for next commit |
37 | | That's it! If everything is done right, you'll see the build process going on TravisCI and after ~20 minutes results will be visible in README.md view on github. |
| 40 | That's it! If everything is done right, you'll see the build process going on TravisCI and after ~20 minutes results will be visible in README.md view on github. |
| 41 | |
| 42 | |
| 43 | |
| 44 | === Coveralls tuning === |
| 45 | |
| 46 | ==== Investigating the results ==== |
| 47 | |
| 48 | After successful run of TravisCI and Coveralls we'll see tests coverage results displayed in README.md view on github. Time to investigate the results! |
| 49 | |
| 50 | * click on the results [https://coveralls.io/r/apolukhin/lexical_cast?branch=develop] |
| 51 | * click on the build number to see detailed coverage description |
| 52 | * click on the source file you wish to investigate |
| 53 | |
| 54 | ==== Setting sources location ==== |
| 55 | Chances are high, that Coveralls will fail to automatically detect source location. In that case you need to |
| 56 | * set "Git repo root directory:" to /home/travis/boost-local/ |
| 57 | * set "Git repo sub directory: :" to include/ (or src/ in case of a source file in src/ folder) |
| 58 | |
| 59 | If everything is done right you'll see the source file with highlighted lines. Green lines are covered by tests, red lines are in binary file and '''are not''' covered by test, gray lines are not in a test's '''binary file''' (there's no code in tests that uses/compile that line). |
| 60 | |
| 61 | ==== Ignoring specified files coverage ==== |
| 62 | Sometimes files from other projects could appear in coverage reports. To disable those files edit `.travis.yml` file and set `IGNORE_COVERAGE=` to files that must be ignored. `IGNORE_COVERAGE` variable understands wildcards, so you could disable files just like this: |
| 63 | {{{ |
| 64 | - IGNORE_COVERAGE='*/boost/progress.hpp */filesystem/src/path.cpp */numeric/conversion/converter_policies.hpp' |
| 65 | }}} |