users@websocket-spec.java.net

[jsr356-users] Re: TCK for WebSocket 1.1?

From: Stuart Douglas <stuart.w.douglas_at_gmail.com>
Date: Thu, 09 Oct 2014 09:53:36 +1100

Joakim Erdfelt wrote:
> That is shocking and disturbing!
>
> Many projects do not have access to the TCK (license incompatibility
> with open source projects).
> Having that much change would indicate that this either isn't a minor
> point release, or the spec was inadequate and is being tightened up.
> It would be one thing, if the open questions on the WEBSOCKET_SPEC jira
> had been answered, but there are still many that haven't even had a
> response yet.

Or it simply means that more tests were added to improve the quality and
test coverage of the TCK.

A similar thing happened between Servlet and Servlet 3.1, where the
number of tests roughly doubled even though it was only a relatively
minor spec update. In this case a lot of the new tests were simply
testing existing spec assertions that were not already covered by the TCK.

I think it is great that the TCK continues to be expanded, as it will
catch more implementation bugs and means less non-standard behaviour
between implementations.

Stuart

> How about another spec pdf with all of the changes?
> Or a version 1.1.1 javadoc update with all of the behavioral changes?
> Or answers to the open questions on the spec jira?
>
>
> --
> Joakim Erdfelt <joakim_at_intalio.com <mailto:joakim_at_intalio.com>>
> webtide.com <http://www.webtide.com/> - intalio.com/jetty
> <http://intalio.com/jetty>
> Expert advice, services and support from from the Jetty & CometD experts
> eclipse.org/jetty <http://eclipse.org/jetty/> - cometd.org
> <http://cometd.org/>
>
> On Wed, Oct 8, 2014 at 1:11 PM, Kevin Sutter <sutter_at_us.ibm.com
> <mailto:sutter_at_us.ibm.com>> wrote:
>
> Hi,
> My normal conduit for the WebSocket expert group is not at work this
> week, so I thought I would try this route to get a quicker
> answer... We're looking to update our WebSocket 1.0 implementation
> to satisfy the new methods introduced by WebSocket 1.1. No big deal
> with that piece. But, we were very surprised by the number of tests
> that the TCK increased by.
>
> For WebSocket 1.0, there were 262 tests. According to the readme
> for the 1.1 TCK, there are now 664 tests! Really? An increase of
> 400 tests for a minor update?
>
> Can somebody help explain this? Or, are we interpreting something
> incorrectly?
>
> Thank you for any insights!
> Kevin
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
> Kevin Sutter
> STSM, Java EE and Java Persistence API (JPA) architect
> mail: sutter_at_us.ibm.com <mailto:sutter_at_us.ibm.com>, Kevin
> Sutter/Rochester/IBM http://webspherepersistence.blogspot.com/
> phone: tl-553-3620 (office), 507-253-3620 <tel:507-253-3620>
> (office) http://openjpa.apache.org/
>
>