Description of problem: Consider running developer modules/cli-tests either in Jenkins or in another environment. The tests have not been running in Jenkins and have not been run manually. When run (requires a running RHQ Server) 16 of 19 tests fail. Some of the failures are due to usage of the CLI API that no longer exists. This is not sufficient to prevent regressions in the CLI.
Version-Release number of selected component (if applicable): RHQ 4.3
100%. per Stefan scrum update 1/17/2012.
Actual results: 16 of 19 CLI tests fail.
Expected results: 19 of 19 tests pass.
Created attachment 555830 [details]
TestNG report from running the tests on my local box. 16 failed tests out of a total of 19.
per scrum 1/23/2012 crouch, loleary, mfoley
(1:22:10 PM) jshaughn: mfoley: Is https://bugzilla.redhat.com/show_bug.cgi?id=782489 still relevant or are these tests basically superseded by your cli automation effort?
(1:22:23 PM) mfoley: 1 sec
(1:22:51 PM) mfoley: we got the CLI automation effort
(1:23:02 PM) mfoley: you can close that BZ
(1:23:06 PM) jshaughn: sweet
(1:23:16 PM) mfoley: or i can do that
(1:23:22 PM) jshaughn: I'll do it
(1:23:35 PM) mfoley: yeah our CLI automation tests are running every night no issues