FWIW, a full run just took 12min for me. 479 tests run w/100% success, 21 skipped
./gradlew cleanAll ./gradlew test reports the report is in build/distributions/reports/tests/index.html Haven’t yet played with cleanTest. > On Mar 16, 2017, at 2:08 PM, Dale LaBossiere <[email protected]> wrote: > > The only ones skipped should be jdbc, kafka, and non-open-mqtt connector > tests. > On OSX one of the FileSteams tests is also skipped. > > If you run ./gradlew reports after/with test you can open your browser on the > report file and get an easier to view report for all results. > > The results will aggregate the test runs in the sense that one test run that > fails for whatever reason creates some results, then if you rerun test it > will skip those successful completed ones and try to run those that didn’t > complete successfully. A report run will collect the latest state of test > runs. > > I think a full run takes >10min on my machine these days. > > I’ll take a look at / try cleanTest, etc. > > — Dale > > >> On Mar 16, 2017, at 1:54 PM, Katherine Marsden <[email protected]> wrote: >> >> I ran ./gradlew cleanTest to clean up the tests but on rerun am seeing a lot >> of UP-TO-DATE tests, e.g. >> >> connectors:serial:testClasses UP-TO-DATE >> :connectors:serial:test UP-TO-DATE >> :connectors:serial:testSummaryFinalizer >> :connectors:wsclient:compileJava UP-TO-DATE >> :connectors:wsclient:processResources UP-TO-DATE >> :connectors:wsclient:classes UP-TO-DATE >> :connectors:wsclient:jar UP-TO-DATE >> >> So, I am not really sure if I have actually run all the tests. >> Below are the summary lines. Does this output look like anything is >> missing? How long should I expect the full run to take? >> >> I assume the skipped ones are expected and require setup that I haven't done. >> >> Best >> >> Kathey >> >> >> :analytics:math3 1.713sec SUCCESS (4 tests, 0 failures, 0 skipped) >> :analytics:sensors 7.979sec SUCCESS (35 tests, 0 failures, 0 skipped) >> :api:execution 0.859sec SUCCESS (2 tests, 0 failures, 0 skipped) >> :api:function 0.884sec SUCCESS (8 tests, 0 failures, 0 skipped) >> :api:oplet 0.860sec SUCCESS (3 tests, 0 failures, 0 skipped) >> :api:topology 1.016sec SUCCESS (3 tests, 0 failures, 0 skipped) >> :api:window 48.522sec SUCCESS (12 tests, 0 failures, 0 skipped) >> :apps:iot 1.741sec SUCCESS (1 tests, 0 failures, 0 skipped) >> :apps:runtime 6.200sec SUCCESS (1 tests, 0 failures, 0 skipped) >> :connectors:command 31.771sec SUCCESS (12 tests, 0 failures, 0 skipped) >> :connectors:csv 1.010sec SUCCESS (2 tests, 0 failures, 0 skipped) >> :connectors:file 156.603sec SUCCESS (56 tests, 0 failures, 2 skipped) >> :connectors:http 7.125sec SUCCESS (20 tests, 0 failures, 0 skipped) >> :connectors:iot 0.904sec SUCCESS (1 tests, 0 failures, 0 skipped) >> :connectors:jdbc 1.061sec SUCCESS (18 tests, 0 failures, 18 skipped) >> :connectors:kafka 0.989sec SUCCESS (1 tests, 0 failures, 1 skipped) >> :connectors:mqtt 89.730sec SUCCESS (24 tests, 0 failures, 0 skipped) >> :connectors:pubsub 4.267sec SUCCESS (8 tests, 0 failures, 0 skipped) >> :connectors:wsclient-javax.websocket 131.406sec SUCCESS (54 tests, 0 >> failures, 0 skipped) >> :console:server 2.169sec SUCCESS (8 tests, 0 failures, 0 skipped) >> :providers:development 47.022sec SUCCESS (69 tests, 0 failures, 0 skipped) >> :providers:direct 62.360sec SUCCESS (101 tests, 0 failures, 0 skipped) >> :runtime:etiao 1.223sec SUCCESS (7 tests, 0 failures, 0 skipped) >> :runtime:jmxcontrol 1.080sec SUCCESS (4 tests, 0 failures, 0 skipped) >> :runtime:jobregistry 1.126sec SUCCESS (5 tests, 0 failures, 0 skipped) >> :runtime:jsoncontrol 1.147sec SUCCESS (6 tests, 0 failures, 0 skipped) >> :spi:topology 1.034sec SUCCESS (1 tests, 0 failures, 0 skipped) >> :test:fvtiot 13.638sec SUCCESS (7 tests, 0 failures, 0 skipped) >> :utils:metrics 0.903sec SUCCESS (6 tests, 0 failures, 0 skipped) >> >> >> BUILD SUCCESSFUL >> Total time: 10 mins 28.354 secs >> >> >
