Hibernate.orgCommunity Documentation

Technology Compatibility Kit Reference Guide for JSR-303: Bean Validation

Specification Lead: Red Hat Inc.

1. Who Should Use This Guide
2. Before You Read This Guide
3. How This Guide Is Organized
I. Getting Acquainted with the TCK
1. Introduction
1.1. TCK Primer
1.2. Compatibility Testing
1.2.1. Why Compatibility Is Important
1.3. About the Bean Validation TCK
1.3.1. Bean Validation TCK Specifications and Requirements
1.3.2. Bean Validation 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
4. Configuration
4.1. TCK Harness Properties
4.2. Configuring TestNG to execute the TCK
4.3. Configuring your build environment to execute the TCK
5. Reporting
5.1. Bean Validation TCK Coverage Metrics
5.2. Bean Validation TCK Coverage Report
5.2.1. Bean Validation 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. Creating the signature file
6.3. Running the signature test
6.4. 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
III. JBoss Test Harness
8. Introduction
8.1. Negotiating the execution of an in-container test
9. Configuration
9.1. JBoss Test Harness Properties
10. Executing a Test Suite
10.1. Building a test suite runner using Maven 2
10.2. Dumping the Test Artifacts to Disk