JON 3.01, RC5 Document CLI assert functionality. It is not documented. Consider including it in API, samples, or elsewhere. Please include it in new CLI documentation plans. +++ This bug was initially created as a clone of Bug #796405 +++ Description of problem: The CLI is documented to have a series of assert* functions available for the scripts to use. These don't work in the server because we fail to bundle testng.jar in server's lib. Version-Release number of selected component (if applicable): 4.3.0-SNAPSHOT How reproducible: always Steps to Reproduce: 1. Create a CLI script with the following body: assertNotNull(null); 2. Define an alert with the above script as a notification 3. Let the alert fire Actual results: The script seems to have succeeded but the server log contains a NoClassDefFoundError of org/testng/Assert. Expected results: The assertion should have executed correctly and produced expected result (in this case, it should throw an AssertionError which should make the notification fail and produce an appropriate error message). Additional info: --- Additional comment from mfoley on 2012-02-22 15:21:15 EST --- can you document a reference to where you see the assert* statements documented? i actually can't find this in the JON documentation (and if it is not documented, clone a doc BZ ... if needed)
Note that unless bug 796680 is fixed for JON 3.0.1 the assert statements *are not* going to work in the server-side CLI script alert notifications. The assert statements *are* working in the standalone CLI regardless of that bug being fixed.
Assert is now asserted: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Operations_Network/100/html/Running_JON_Command-Line_Scripts/cli-ref-api.html#interactive-cli
Closing.