Several of the server command line tools report a hardcoded version of "0.1". Some of these tools can also be broken without causing an obvious failure in the unittest suite. A sanity check test that ensures the output of "<command> --version" matches the expected Beaker for version for each of these scripts would ensure that: 1. At least import failures resulting from changes in other parts of the code will be detected by the test suite, even if full operation of the tool is not yet covered. 2. The tools report the correct version.
(In reply to Nick Coghlan from comment #0) > > A sanity check test that ensures the output of "<command> --version" matches > the expected Beaker for version for each of these scripts would ensure that: > hi, what is the specific command for version check tests? thanks.
Documenting the server utilities is covered by bug 970403 The approximate list is given by the "console_scripts" entry in the server setup.py: http://git.beaker-project.org/cgit/beaker/tree/Server/setup.py.in?h=develop#n203
http://gerrit.beaker-project.org/5353
This picked up a few other pre-existing problems with stderr spew, so it was definitely worthwhile. http://gerrit.beaker-project.org/5354 beaker-repo-update: don't spew pointless warnings about RHEL repos http://gerrit.beaker-project.org/5355 beaker-create-kickstart: fix unicode warnings http://gerrit.beaker-project.org/5356 tests: run server commands in subprocesses wherever possible
This bug fix is included in beaker-server-24.0-0.git.194.c515848 which is currently available for download here: https://beaker-project.org/nightlies/develop/
Beaker 24.0 has been released.