Setup and Configuration

Previous Next Contents

4 Setup and Configuration

Note

The Jakarta EE Specification process provides for any number of compatible implementations. As additional implementations become available, refer to project or product documentation from those vendors for specific TCK setup and operational guidance.

This chapter describes how to set up the Authentication TCK. Before proceeding with the instructions in this chapter, be sure to install all required software, as described in Chapter 3, "Installation."

After completing the instructions in this chapter, proceed to Chapter 5, "Executing Tests," for instructions on running the Authentication TCK.

Note

In these instructions, variables in angle brackets need to be expanded for each platform. For example, <JAVA_HOME> becomes $JAVA_HOME on Solaris/Linux and %JAVA_HOME% on Windows. In addition, the forward slashes (/) used in all of the examples need to be replaced with backslashes (\) for Windows. Finally, be sure to use the appropriate separator for your operating system when specifying multiple path entries (; on Windows, : on UNIX/Linux).

On Windows, you must escape any backslashes with an extra backslash in path separators used in any of the following properties, or use forward slashes as a path separator instead.

4.1 Download the Jakarta Authentication TCK

The Jakarta Authentication TCK is retrieved from

https://download.eclipse.org/jakartaee/authentication/3.0/jakarta-authentication-tck-3.0.1.zip

4.2 Setting up an Evironment for the Maven Surefire based TCK Against a Compatible Implementation

The current JUnit based set of tests runs under a Maven surefire runner and needs a profile configured for your compatible implementation to test. The top level tck/pom.xml includes example profiles including one for GlassFish. To configuration a profile for your compatible implementation, start with the GlassFish glassfish-ci-managed profile, and modify the dependencies and configuration to support your implementation and Arqulillian container implementation. The Arqulillian container implementation starts up your container and deploys the test wars into it.

4.3 Setting up an Evironment Against a Jakarta EE 10.0 CI for legacy TCK tests

The legacy tests which are part of the latest Jakarta Authentication TCK use KEYWORDS parameter to identify the tests that need to be executed for JakartaEE Full and Web profile implementations. The tck/old-tck/run/pom.xml includes example of using the profiles platform (for JakartaEE Platform - Full profile by default) and web (for Web Profile) that sets the appropirate values for KEYWORDS in the CI.

For JakartaEE Platform Full profile , KEYWORDS = jaspic_baseline|javaee
For JakartaEE Platform Web platform , KEYWORDS = jaspic_web_profile

The tck/old-tck/source/src/com/sun/ts/lib/harness/keyword.properties has the full list of keywords mapped to the test directories in tck/old-tck/


Previous Next Contents
Eclipse Foundation Logo  Copyright © 2017, 2021 Oracle and/or its affiliates. All rights reserved.