SeamFramework.orgCommunity Documentation

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

Specification Lead: Red Hat Inc.

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. Configuring TestNG to execute the TCK
4.4. Configuring your build environment to execute the TCK
5. Reporting
5.1. CDI TCK Coverage Metrics
5.2. CDI TCK Coverage Report
5.2.1. CDK TCK Assertions
5.2.2. Producing the Coverage Report
5.2.3. TestNG Reports
II. Executing and Debugging Tests
6. Executing the Test Suite
6.1. The Test Suite Runner
6.2. Running the Tests In Standalone Mode
6.3. Running the Tests In the Container
6.4. Dumping the Test Artifacts
7. Running Tests in Eclipse
7.1. Leveraging Eclipse's plugin ecosystem
7.2. Readying the Eclipse workspace
7.3. Running a test in standalone mode
7.4. Running integration tests
8. Debugging Tests in Eclipse
8.1. Debugging a standalone test
8.2. Debugging an integration test
8.2.1. Attaching the IDE debugger to the container
8.2.2. Launching the test in the debugger
III. JBoss Test Harness
9. Introduction (JBoss Test Harness)
9.1. Negotiating the execution of an in-container test
10. Configuration
10.1. JBoss Test Harness Properties
11. Executing a Test Suite
11.1. Building a test suite runner using Maven 2
11.2. Dumping the Test Artifacts to Disk