Preface

## Preface

This guide describes how to install, configure, and run the Technology Compatibility Kit (TCK) that is used to test the JavaMail API (JavaMail 1.6) (JSR 919) technology.

The JavaMail TCK is a portable, configurable automated test suite for verifying the compatibility of a licensee’s implementation of the JavaMail 1.6 Specification (hereafter referred to as the licensee implementation). The JavaMail TCK uses the JavaTest harness version 5.0 to run the test suite

Note | Note All references to specific Web URLs are given for the sake of your convenience in locating the resources quickly. These references are always subject to changes that are in many cases beyond the control of the authors of this guide.

Refer to the Java Licensee Engineering (https://javapartner.oracle.com) Web site for answers to frequently asked questions and send questions you may have to your Java Licensee Engineering contact.

### Who Should Use This Book

This guide is for licensees of the JavaMail 1.6 technology to assist them in running the test suite that verifies compatibility of their implementation of the JavaMail 1.6 Specification.

### Documentation Accessibility

For information about Oracle’s commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

### Before You Read This Book

You should be familiar with the JavaMail 1.6 Specification, which can be found at http://jcp.org/en/jsr/detail?id=919.

Before running the tests in the JavaMail TCK, you should familiarize yourself with the JavaTest documentation that is included in the JavaMail TCK documentation bundle.

### Typographic Conventions

The following table describes the typographic conventions that are used in this book.

Convention | Meaning | Example
--- | --- | ---
Boldface | Boldface type indicates graphical user interface elements associated with an action, terms defined in text, or what you type, contrasted with onscreen computer output. | From the File menu, select Open Project. A cache is a copy that is stored locally. `machine_name% su` `Password:`
`Monospace` | Monospace type indicates the names of files and directories, commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. | Edit your `.login` file. Use `ls` `-a` to list all files. `machine_name% you have mail.`
Italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. | Read Chapter 6 in the User’s Guide. Do not save the file. The command to remove a file is `rm` filename.

### Shell Prompts in Command Examples

The following table shows the default UNIX system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.

Shell | Prompt
--- | ---
C shell | `machine_name%`
C shell for superuser | `machine_name#`
Bourne shell and Korn shell | `$`
Bourne shell and Korn shell for superuser | `#`
Bash shell | `shell_name-shell_version$`
Bash shell for superuser | `shell_name-shell_version#`

Copyright © 2017, Oracle and/or its affiliates. All rights reserved.