Specifying Exclude Lists With excludeList

# Specifying Exclude Lists With `excludeList`

Test suites can supply exclude list files which contain the list of tests that the harness is not required to run. Exclude list files conventionally use a `.jtx` extension. Once you have set up a configuration, you can use an `excludeList` command to specify the exclude list for your test run:

> jtharness ... [initial-setup-commands] ... `-excludeList` path/filename1 path/filename2 ... [task-command]

For example, to specify multiple path/filename arguments , issue the `-excludeList` command once followed by multiple path/filename arguments separated by spaces. For example:

> jtharness ... [initial-setup-commands] ...`-excludeList aaaa.jtx bbb.jtx C:\myconfig\cc.jtx` ... [taskcommand]

Note, because a space is a separator, file path arguments cannot contain spaces (for example, `C:\Program Files\myconfig\foobar` will not work).

See About the Command-Line Examples for a description of the use of > jtharness.

See Command-Line Overview for a detailed description of the command-line structure.

The exclude list that you specify in the command line overrides any exclude list specified in the configuration file without changing the configuration file. To specify an exclude list, include the commands in the following sequence:

1. Include the commands required to set up a configuration.See Setup Commands for a description of the commands.

2. Include the commands to specify an exclude list (`excludeList` path/filename).
3. (Optional) Include a task command (such as `runtests`).
   See Task Commands for the commands that you can include.

## Detailed Example of `excludeList` Command

In the following example, myconfig`.jti` and myexcludelist`.jtx` represent file names that might exist on your system.

Command Options Format Example:

> jtharness `-config` myconfig`.jti -excludeList` myexcludelist`.jtx -runtests`

See Formatting a Command for descriptions and examples of other command formats that you can use.

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