[CONF] Apache Tomcat > WebSocket 1.1 TCK

[Mark Thomas (Confluence)]

Title: Message Title

There's 2 new edits on this page

WebSocket 1.1 TCK Mark Thomas edited this page Here's what changed: ... Test Suite Download latest nightly promoted build httpshttp://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/websockettckjakartaee8/promoted/websocket-tck-1.1_latest.1.zip Extract to WEBSOCKET_TCK_HOME ... Accept the defaults and then run the tests Expected results ( ... Java EE ... 8) A default 109.0.x build running with the nightly TCK build (as of 2020yyyy-05mm-13dd) without any configuration triggers 10 20 test failures 2 unclear specification 2 x URI https://github.com/eclipse-ee4j/websocket-api/issues/228 PR to exclude https://github.com/eclipse-ee4j/jakartaee-tck/pull/263 3 faulty tests 1 x signature tests PR to update signatures in TCK https://github.com/eclipse-ee4j/jakartaee-tck/pull/256 2 x faulty timeout tests https://github.com/eclipse-ee4j/jakartaee-tck/issues/260 PR to fix the tests https://github.com/eclipse-ee4j/jakartaee-tck/pull/261 5 Tests 'fixed' by appropriate system property configuration (see above). No need for the server.xml changes. 4 x extensions (TCK assumes invalid extensions are ignored) Consider making TCK smarter so it ignores other extensions the server may advertise. Better still, detect them first and then exclude them from this test. Need to discuss expected behaviour if an unknown extension is specified. Are these required or optional? 1 x timeout related test expects more frequent expiration checks Expected results (Java EE 8) A default 9.0.x build without any configuration triggers 20 test failuresTo be confirmed. Tomcat 9 was last tested with a nightly build of the WebSocket 1.1 TCK. It has yet to be tested with the 1.1.1 release of the TCK. 2 unclear specification 2 x URI https://github.com/eclipse-ee4j/websocket-api/issues/228 ... Go to page history View page

Stop watching space • Manage notifications This message was sent by Atlassian Confluence 7.5.0