Changeset 4355
- Timestamp:
- 25 Jun 2009, 10:05:28 (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
waeup/branches/ulif-rewrite/src/waeup/doc/developernotes.txt
r4352 r4355 35 35 * A subversion client (svn) 36 36 37 * enscript (enscript) [optional] 38 39 This is only needed if you want test coverage reports. 40 37 41 All these packages can be installed on Debian systems like this:: 38 42 39 43 # apt-get install python2.5 python2.5-dev python2.5-dbg \ 40 gcc libc6-dev svn 44 gcc libc6-dev svn enscript 41 45 42 46 Afterwards you should be able to enter:: … … 282 286 line was used in tests. 283 287 288 To have a more convenient cmdline interface, we also provide some 289 shortcuts:: 290 291 $ bin/coverage-detect 292 293 will run all the tests as shown above and put the results in 294 ``parts/coverage-detect/coverage``. 295 296 After that you can run:: 297 298 $ bin/coverage-report 299 300 to get a browsable HTML representation of test coverage in 301 ``parts/coverage-detect/coverage/report``. 302 303 Both, the coverage reports and HTML documentation generated by sphinx 304 can be packed and put onto a website as-is. 305 306 It is also possible to generate the docs and reports nightly by a 307 buildbot or something like this.
Note: See TracChangeset for help on using the changeset viewer.