sun.com docs.sun.com | My Sun Worldwide Sites

|  | Products |  | Downloads |  | Service & Solutions |  | Support |  | Training |  | Research

| Previous Contents Next
- Chapter 1 # Introduction This chapter provides an overview of the principles that apply generally to all Technology Compatibility Kits (TCKs) and describes the SOAP with Attachments API for Java 1.3 TCK (SAAJ TCK 1.3). It also includes a high level listing of what is needed to get up and running with the SAAJ TCK. ## 1.1 Compatibility Testing Compatibility testing differs from traditional product testing in a number of ways. The focus of compatibility testing is to test those features and areas of an implementation that are likely to differ across other implementations, such as those features that: Rely on hardware or operating system-specific behavior Are difficult to port Mask or abstract hardware or operating system behavior Compatibility test development for a given feature relies on a complete specification and reference implementation for that feature. Compatibility testing is not primarily concerned with robustness, performance, or ease of use. ### 1.1.1 Why Compatibility Testing is Important Java platform compatibility is important to different groups involved with Java technologies for different reasons: Compatibility testing is the means by which Sun Microsystems ensures that the Java platform does not become fragmented as it is ported to different operating systems and hardware environments. Compatibility testing benefits developers working in the Java programming language, allowing them to write applications once and then to deploy them across heterogeneous computing environments without porting. Compatibility testing allows application users to obtain applications from disparate sources and deploy them with confidence. Conformance testing benefits Java platform implementors by ensuring a level playing field for all Java platform ports. ### 1.1.2 TCK Compatibility Rules Compatibility criteria for all technology implementations are embodied in the TCK Compatibility Rules that apply to a specified technology. Each TCK tests for adherence to these Rules as described in Chapter 2. ### 1.1.3 TCK Overview A TCK is a set of tools and tests used to verify that a licensee's implementation of Sun Microsystems's technology conforms to the applicable specification. All tests in the TCK are based on the written specifications for the Java platform. A TCK tests compatibility of a licensee's implementation of Sun Microsystems's technology to the applicable specification of the technology. Compatibility testing is a means of ensuring correctness, completeness, and consistency across all implementations developed by Sun Microsystems technology licensees. The set of tests included with each TCK is called the test suite. Most tests in a TCK's test suite are self-checking, but some tests may require tester interaction. Most tests return either a Pass or Fail status. For a given platform to be certified, all of the required tests must pass. The definition of required tests may change from platform to platform. The definition of required tests will change over time. Before your final certification test pass, be sure to download the latest Exclude List for the TCK you are using. ### 1.1.4 Java Community Process (JCP) Program and Compatibility Testing The Java Community Process™ (JCP) program is the formalization of the open process that Sun Microsystems, Inc. has been using since 1995 to develop and revise Java technology specifications in cooperation with the international Java community. The JCP program specifies that the following three major components must be included as deliverables in a final Java technology release under the direction of the responsible Expert Group: Technology Specification Reference Implementation Technology Compatibility Kit (TCK) For further information about the JCP program, go to Java Community Process. ## 1.2 About the SAAJ TCK 1.3 The SAAJ TCK 1.3 is designed as a portable, configurable, automated test suite for verifying the compatibility of a licensee's implementation of Sun Microsystems's SAAJ 1.3 Specification. ### 1.2.1 SAAJ TCK Specifications and Requirements This section lists the applicable requirements and specifications. Specification Requirements -- Software requirements for a SAAJ implementation are described in detail in the SAAJ 1.3 Specification. Links to the SAAJ specification and other product information can be found at http://jcp.org/aboutJava/communityprocess/maintenance/jsr067/index2.html. SAAJ Version -- The SAAJ TCK 1.3 is based on the SAAJ Specification, Version 1.3. Reference Runtime -- The designated Reference Runtime for conformance testing of implementations based upon the SAAJ Specification 1.3 is the Sun Microsystems SAAJ 1.3 Reference Implementation (RI). See the SAAJ RI Installation Guide at http://java.sun.com/webservices/saaj/index.jsp for setup instructions. ### 1.2.2 SAAJ TCK Components The SAAJ TCK 1.3 includes the following components: JavaTest harness version 3.2.1 and related documentation. See the `README-javatest.html` file, the JavaTest Users Guide, and the `ReleaseNotes-javatest.html` file for additional information. SAAJ TCK signature tests; check that all public APIs are supported and/or defined as specified in the SAAJ Version 1.3 implementation under test. API tests for all of the SAAJ API in all related packages:
      javax.xml.soap
End-to-end tests that demonstrate sending/receiving SOAP messages to/from a URL endpoint as well tests for WSI compliance.. The SAAJ TCK tests have been tested with the following: SAAJ 1.3 Reference Implementation Java Standard Edition 5 The SAAJ TCK tests run on the following platforms: Solaris 9 Operating System on Sparc and x86 Solaris 10 Operating System on Sparc and Opteron Windows 2003 Server Professional Edition Windows XP Professional Edition Windows 2000 Professional Edition RedHat Linux 9.0 RedHat Linux AS 3.0 (including Update 4)
| Previous Contents Next

Company Info Contact Terms of Use Privacy Copyright 1994-2006 Sun Microsystems, Inc.