The Full Wiki

Technology Compatibility Kit: Wikis

Advertisements

Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.

Encyclopedia

From Wikipedia, the free encyclopedia

A Technology Compatibility Kit (TCK) is a suite of tests that at least nominally checks a particular alleged implementation of a Java Specification Request (JSR) for compliance. It is one of the three required pieces for a ratified JSR in the Java Community Process, which are :

  • the JSR specification
  • the JSR reference implementation
  • the Technology Compatibility Kit (TCK)

Contents

Contents and architecture

TCKs tend to be obtained from the Specification Lead of a given JSR. They usually (but not always) consist of a graphical host application which communicates over TCP/IP with the device or Java virtual machine that is under test. Tests are typically obtained by the device over HTTP, and results are posted back to the host application in a similar way. This decoupling enables TCKs to be used to test virtual machines on devices such as CLDC mobile phones which do not have the power to run the full TCK host application.

The tests contained in the JSR are supposedly derived from the statements in the JSR specification. Any given API will have a set of tests to ensure that it behaves in the intended way, including in error conditions.

In order to state conformance with a given JSR, a Java implementation has to pass the associated TCK. Any (rare) exceptions have to be negotiated with the specification lead. Because of this, TCKs are of great importance when implementing a JSR. The first great milestone is to get the TCK running in the first place, which necessarily involves the Java implementation and underlying networking stack having a certain level of maturity. Next, the TCK must be properly configured - because they must be flexible enough to cope with any implementation, there are many options. (For example, listing all the supported media formats and associated optional controls for JSR135). Particular tests also require some setup activity - this tends to be particularly complex for the tests which ensure correct behaviour in error conditions, because the Java implementation must be put in the right state to cause each error. Finally, each failing test must be fixed, which is usually handled by the usual defect tracking mechanisms.

Some Java implementors consider their product to be mainly complete once the TCKs pass. Whilst it's true that the TCKs are quite comprehensive, there are many areas that they do not cover. These include performance, as well as the optional features. There's no alternative but to do lots of real-world testing to address these shortcomings, although additional test suites such as JDTS may help.

TCK for the Java platform

The Technology Compatibility Kit for a particular Java platform is called Java Compatibility Kit (JCK). It is an extensive test suite used by Sun Microsystems and licensees to ensure compatible implementations of the platform.

The JCK for Java 6.0 source code has been released[1][2]. The associated license did not initially allow users to compile or run the tests[3], but the right to see the code is not associated with tainting concerns, and public comments on the source code are allowed[1]. However, since the release of OpenJDK, a specific license allow to run the JCK in the OpenJDK context, that is for any GPL implementation deriving substantially from OpenJDK [4][5].

TCK framework

The JavaTest harness tool is today the most common unit testing framework used to verify the implementation compliance. It is a general purpose testing framework designed to run TCK tests. However, some specifications are also using JUnit.

See also

Java Community Process

References

  1. ^ a b Hamilton, Graham (2004-12-13). "J2SE Compatibility Test Sources Released". http://weblogs.java.net/blog/kgh/archive/2004/12/j2se_compatibil.html. Retrieved 2008-03-08. "We have tried to make sure the license meets the reasonable needs of developers who want to evaluate the JCK sources: It's available at zero cost, through a click-through license; There is no "tainting". Once you delete your copy of the JCK, you aren't constrained in your future actions. To try to make this really clear, we included a section explicitly granting what the lawyers call "residual rights", which basically means that stuff that sticks in your head is OK to use in the future; You can publish feedback and comments publicly."  
  2. ^ JCK project
  3. ^ ""READ ONLY" SOURCE LICENSE AGREEMENT, v1.0 JAVA (TM) COMPATIBILITY KIT 6a". Sun Microsystems. June 2007. https://jck.dev.java.net/jck-read-only-license.txt. Retrieved 2008-03-08.  
  4. ^ Darcy, Joseph (2008-03-06). "Matching JDK and JCK Versions". http://blogs.sun.com/darcy/entry/matching_jdk_and_jck_versions. Retrieved 2008-03-08. "If you're interested in running the JCK in context of OpenJDK projects, a license is available."  
  5. ^ "OPENJDK COMMUNITY TCK LICENSE AGREEMENT V 1.1" (PDF). Sun Microsystems. http://openjdk.java.net/legal/openjdk-tck-license.pdf. Retrieved 2008-03-08. "Subject to and conditioned upon its Licensee Implementation being substantially derived from OpenJDK Code and, if such Implementation has or is to be distributed to a third party, its being distributed under the GPL License, Sun hereby grants to Licensee, to the extent of Sun's Intellectual Property Rights in the TCK, a worldwide, personal, non-exclusive, non-transferable, limited license to use the TCK internally and solely for the purpose of developing and testing Licensee Implementation."  

External links

Advertisements

Advertisements






Got something to say? Make a comment.
Your name
Your email address
Message