1## Need for CI 2 3Generally if we're adding something that's supposed to work ongoing, the stuff 4should be exercised in CI (at least Travis). 5 6If there are few users for a particular feature, experience has shown that 7refactors or other upheaval can easily break it into a state of uselessness 8without anyone noticing until later. 9 10Therefore here's a description of how to add something to the CI tests... this 11is certainly a nonproductive PITA and I have never been thanked for the work 12involved. But if the promise of the various features working is going to 13remain alive, it's necessary to include CI test where possible with new 14nontrivial code. 15 16## Integration points 17 18### cmake 19 20`.travis.yml` maps the various test activities to CMake options needed. 21 22### including dependent packages into travis 23 24See `./scripts/travis_install.sh` 25 26### performing prepared test actions 27 28See `./scripts/travis_control.sh` 29 30