You only appear to be running the tests written directly in C. Many of the tests are written in Python and are run against proton-c and proton-j. Taking a quick guess, you might not have python and a JDK installed (or at least, cmake didnt find one/both of them), which would mean the build didnt create the python bindings or run the tests against proton-j.
On 22 May 2015 at 01:17, Deb Haldar <[email protected]> wrote: > Hi Folks, I had a quick question on running proton C tests to > checkregressions after my modification. So far I’m doing the following: > - Running ctest to execute the following tests: Start > 1:c-object-tests1/7 Test #1: c-object-tests ................... Passed > 0.54 sec Start 2:c-message-tests2/7 Test #2: c-message-tests > .................. Passed 0.37 sec Start 3:c-engine-tests3/7 Test #3: > c-engine-tests ................... Passed 0.33 sec Start > 4:c-parse-url-tests4/7 Test #4: c-parse-url-tests ................ Passed > 0.25 sec Start 5:c-refcount-tests5/7 Test #5: c-refcount-tests > ................. Passed 0.22 sec Start 6:c-reactor-tests6/7 Test #6: > c-reactor-tests .................. Passed 0.69 sec Start > 7:c-event-tests7/7 Test #7: c-event-tests .................... Passed > 0.21 sec 100% tests passed, 0 tests failed out of 7 Total Test time (real) = > 2.77 sec > - Running the Java Broker and user send.exe +recv.exe and send-async.exe > and recv-async.exe for functional testing. > Is there any other test that I should be running for regressiontesting ? > Thanks, > Deb. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
