Introduction |
Previous | Next | Contents |
This chapter provides an overview of the principles that apply generally to all Technology Compatibility Kits (TCKs) and describes the Java Message Service TCK (JMS TCK 2.0) (JSR 343). It also includes a high level listing of what is needed to get up and running with the JMS TCK.
This chapter includes the following topics:
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.
Java platform compatibility is important to different groups involved with Java technologies for different reasons:
Compatibility testing 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.
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, "Procedure for Certification."
A TCK is a set of tools and tests used to verify that a licensee’s implementation of a Java EE 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 the technology to the applicable specification of the technology. Compatibility testing is a means of ensuring correctness, completeness, and consistency across all implementations developed by 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.
The Java Community Process (JCP) program is the formalization of the open process that has been used 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 (http://jcp.org/en/home/index).
The JMS TCK 2.0 is designed as a portable, configurable, automated test suite for verifying the compatibility of a licensee’s implementation of the JMS 2.0 Specification.
This section lists the applicable requirements and specifications.
Specification Requirements: Software requirements for a JMS implementation are described in detail in the JMS 2.0 Specification. Links to the JMS specification and other product information can be found at http://jcp.org/en/jsr/detail?id=343.
JMS Version: The JMS TCK 2.0 is based on the JMS Specification, Version 2.0.
Reference Implementation: The JMS 2.0 Reference Implementation (OpenMQ) is available from Java Licensee Engineering (https://javapartner.oracle.com). See the RI documentation page at http://openmq.github.io for more information.
See the JMS TCK Release Notes for more specific information about Java SE version requirements, supported platforms, restrictions, and so on.
The JMS TCK 2.0 includes the following components:
JavaTest harness version 5.0 and related documentation. See the
ReleaseNotes-jtharness.html
file and the
JT Harness web site
for additional information.
JMS TCK signature tests; check that all public APIs are supported and/or defined as specified in the JMS Version 2.0 implementation under test.
If applicable, an exclude list, which provides a list of tests that your implementation is not required to pass.
API tests for all of the JMS API in all related packages:
javax.jms
The JMS TCK tests run on the following platforms:
Windows 10
Oracle Linux 7.1
The JavaTest harness version 5.0 is a set of tools designed to run and manage test suites on different Java platforms. The JavaTest harness can be described as both a Java application and a set of compatibility testing tools. It can run tests on different kinds of Java platforms and it allows the results to be browsed online within the JavaTest GUI, or offline in the HTML reports that the JavaTest harness generates.
The JavaTest harness includes the applications and tools that are used for test execution and test suite management. It supports the following features:
Sequencing of tests, allowing them to be loaded and executed automatically
Graphic user interface (GUI) for ease of use
Automated reporting capability to minimize manual errors
Failure analysis
Test result auditing and auditable test specification framework
Distributed testing environment support
To run tests using the JavaTest harness, you specify which tests in the test suite to run, how to run them, and where to put the results as described in Chapter 4, "Setup and Configuration."
The test suite is the collection of tests used by the JavaTest harness to test a particular technology implementation. In this case, it is the collection of tests used by the JMS TCK 2.0 to test a JMS 2.0 implementation. The tests are designed to verify that a licensee’s runtime implementation of the technology complies with the appropriate specification. The individual tests correspond to assertions of the specification.
The tests that make up the TCK compatibility test suite are precompiled and indexed within the TCK test directory structure. When a test run is started, the JavaTest harness scans through the set of tests that are located under the directories that have been selected. While scanning, the JavaTest harness selects the appropriate tests according to any matches with the filters you are using and queues them up for execution.
Each version of a TCK includes an Exclude List contained in a .jtx
file. This is a list of test file URLs that identify tests which do not
have to be run for the specific version of the TCK being used. Whenever
tests are run, the JavaTest harness automatically excludes any test on
the Exclude List from being executed.
A licensee is not required to pass or run any test on the Exclude List.
The Exclude List file, <TS_HOME>/bin/ts.jtx
, is included in the
JMS TCK.
Note
|
From time to time, updates to the Exclude List are made available on the Java Licensee Engineering (https://javapartner.oracle.com) Web site. You should always make sure you are using an up-to-date copy of the Exclude List before running the JMS TCK to verify your implementation. |
A test might be in the Exclude List for reasons such as:
An error in an underlying implementation API has been discovered which does not allow the test to execute properly.
An error in the specification that was used as the basis of the test has been discovered.
An error in the test itself has been discovered.
The test fails due to a bug in the tools (such as the JavaTest harness, for example).
In addition, all tests are run against the reference implementations. Any tests that fail when run on a reference Java platform are put on the Exclude List. Any test that is not specification-based, or for which the specification is vague, may be excluded. Any test that is found to be implementation dependent (based on a particular thread scheduling model, based on a particular file system behavior, and so on) may be excluded.
Note
|
Licensees are not permitted to alter or modify Exclude Lists. Changes to an Exclude List can only be made by using the procedure described in Section 2.3.1, "TCK Test Appeals Steps." |
You need to set several variables in your test environment, modify
properties in the <TS_HOME>/bin/ts.jte
file, and then use the JavaTest
harness to configure and run the JMS tests, as described in
Chapter 4, "Setup and Configuration."
This section provides an general overview of what needs to be done to install, set up, test, and use the JMS TCK. These steps are explained in more detail in subsequent chapters of this guide.
Make sure that the following software has been correctly installed on the system hosting the JavaTest harness:
Java SE 8
JMS 2.0 RI, which is OpenMQ
JMS TCK version 2.0, which includes:
JDOM 1.0
Apache Commons HTTP Client 3.1
Apache Commons Logging 1.1.1
Apache Commons Codec 1.3
The JMS 2.0 Vendor Implementation (VI)
See the documentation for each of these software applications for
installation instructions. See Chapter 3,
"Installation," for instructions on installing the JMS TCK.
Set up the JMS TCK software.
See Chapter 4, "Setup and Configuration," for
details about the following steps.
Set up your shell environment.
Modify the required properties in the <TS_HOME>/bin/ts.jte
file.
Configure the JavaTest harness.
Test the JMS 2.0 implementation.
Test the JMS implementation installation by running
the test suite. See Chapter 5, "Executing Tests."
Previous | Next | Contents |