SeamFramework.orgCommunity Documentation

Technology Compatibility Kit Reference Guide for JSR-299: Context and Dependency Injection for Java EE

Specification Lead: Red Hat Inc.

Gavin King

JSR-299: Contexts and Dependency Injection (CDI) for Java EE specification lead (Red Hat, Inc.)

Pete Muir

CDI TCK lead (Red Hat, Inc.)

Dan Allen

CDI TCK developer (Red Hat, Inc.)

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,  
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Copyright © 2009 Red Hat Inc., and individual contributors listed as authors.

Preface
1. Who Should Use This Book
2. Before You Read This Book
3. How This Book Is Organized
I. Getting Acquainted with the TCK
1. Introduction (CDI TCK)
1.1. TCK Primer
1.2. Compatibility Testing
1.2.1. Why Compatibility Is Important
1.3. About the CDI TCK
1.3.1. CDI TCK Specifications and Requirements
1.3.2. CDI TCK Components
2. Appeals Process
2.1. Who can make challenges to the TCK?
2.2. What challenges to the TCK may be submitted?
2.3. How these challenges are submitted?
2.4. How and by whom challenges are addressed?
2.5. How accepted challenges to the TCK are managed?
3. Installation
3.1. Obtaining the Software
3.2. The TCK Environment
3.3. Eclipse Plugins
3.3.1. TestNG Plugin
3.3.2. Maven 2 Plugin (m2eclipse)
4. Configuration
4.1. TCK Harness Properties
4.2. The Porting Package
4.3. Using the CDI TCK with the Java EE Web Profile
4.4. Using custom deployment descriptors
4.5. Configuring TestNG to execute the TCK
4.6. Configuring your build environment to execute the TCK
4.7. Configuring your application server to execute the TCK
5. Reporting
5.1. CDI TCK Coverage Metrics
5.2. CDI TCK Coverage Report
5.2.1. CDI TCK Assertions
5.2.2. Producing the Coverage Report
5.2.3. TestNG Reports
II. Executing and Debugging Tests
6. Running the Signature Test
6.1. Obtaining the sigtest tool
6.2. Running the signature test
6.3. Forcing a signature test failure
7. Executing the Test Suite
7.1. The Test Suite Runner
7.2. Running the Tests In Standalone Mode
7.3. Running the Tests In the Container
7.4. Dumping the Test Artifacts
8. Running Tests in Eclipse
8.1. Leveraging Eclipse's plugin ecosystem
8.2. Readying the Eclipse workspace
8.3. Running a test in standalone mode
8.4. Running integration tests
9. Debugging Tests in Eclipse
9.1. Debugging a standalone test
9.2. Debugging an integration test
9.2.1. Attaching the IDE debugger to the container
9.2.2. Launching the test in the debugger
III. JBoss Test Harness
10. Introduction (JBoss Test Harness)
10.1. Negotiating the execution of an in-container test
11. Configuration
11.1. JBoss Test Harness Properties
12. Executing a Test Suite
12.1. Building a test suite runner using Maven 2
12.2. Dumping the Test Artifacts to Disk