Hi Kevin,
TCK test suite developer work sometimes does not end when initial
version is released - in this case, there were some tests which were
added to the suite after 1.0 release and those were included in 1.1
version of the test suite. From what I know, this is not unusual in TCK
suite development lifecycle - they release the suite only when there are
some issues (excluding tests) or when the new version of the
specification is released (adding tests and improving test coverage).
Does that make sense?
Regards,
Pavel
On 08/10/14 13:11, Kevin Sutter 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, Kevin Sutter/Rochester/IBM
> http://webspherepersistence.blogspot.com/
> phone: tl-553-3620 (office), 507-253-3620 (office)
> http://openjpa.apache.org/