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