Websocket tests were disabled because they were "unstable".
I've therefore migrated these from htmlunit to selenium+chrome. It runs fine for me.
Only change is that I've merged all (well, two) test classes into one. Because, still for unclear reason, on any second test class sending the push will always fail, regardless which test class begun. This is most probably a selenium+webdriver bug.
Websocket tests were disabled because they were "unstable".
I've therefore migrated these from htmlunit to selenium+chrome. It runs fine for me.
Only change is that I've merged all (well, two) test classes into one. Because, still for unclear reason, on any second test class sending the push will always fail, regardless which test class begun. This is most probably a selenium+webdriver bug.
NOTE: while running these I discovered a CDI bug in Mojarra 4.1, this has been fixed https://github.com/eclipse-ee4j/mojarra/pull/5403 but it needs to be merged before this TCK change.