|
9 | 9 | # should be taken to handle test failures of intermittent or
|
10 | 10 | # randomness tests.
|
11 | 11 | #
|
12 |
| -# A "headful" test requires a graphical environment to meaningfully |
13 |
| -# run. Tests that are not headful are "headless". |
14 |
| -# A test flagged with key sound needs audio devices on the system, this |
15 |
| -# may be accompanied by the headful keyword since audio device access |
| 12 | +# A test flagged with cgroups uses cgroups. |
| 13 | +# |
| 14 | +# Notes on "client" keywords : headful sound printer multimon |
| 15 | +# =========================================================== |
| 16 | +# |
| 17 | +# These keywords are there to help with test selection so that |
| 18 | +# tests that need a particular resource can be selected to run on a system |
| 19 | +# with that resource. Conversely "!somekeyword" can be used to exclude tests |
| 20 | +# on a system without such a resource. |
| 21 | +# Caution: If you are always excluding tests using any of these keywords then you |
| 22 | +# are likely missing many important tests. |
| 23 | +# |
| 24 | +# "headful". A "headful" test requires a graphical environment to meaningfully run. |
| 25 | +# This does not have to mean a physical host, since a VM can be configured as headful. |
| 26 | +# Tests that are not headful are "headless". |
| 27 | +# Note: all manual tests are assumed to be headful and do not need the keyword. |
| 28 | +# |
| 29 | +# "printer". Not all tests of printing APIs require a printer, but many do. |
| 30 | +# So a "printer" test requires a printer to be installed to do anything meaningful. |
| 31 | +# Tests may not fail if there is none, instead just silently return. |
| 32 | +# But they also may legitimately throw an Exception depending on the test. |
| 33 | +# Also printer tests are not necessarily headful, but some are, and some are automated. |
| 34 | +# |
| 35 | +# "sound". Similarly, not all sound tests require audio devices, but many do. |
| 36 | +# A test flagged with key "sound" needs audio devices on the system. |
| 37 | +# Also they are not necessarily "headful", since they don't require a display etc. |
| 38 | +# But sometimes they may be accompanied by the headful keyword, since sound |
16 | 39 | # is often linked to access to desktop resources and headful systems are
|
17 | 40 | # also more likely to have audio devices (ie meaning both input and output)
|
18 |
| -# A test flagged with key "printer" requires a printer to succeed, else |
19 |
| -# throws a PrinterException or the like. |
20 |
| -# A test flagged with cgroups uses cgroups. |
| 41 | +# |
| 42 | +# "multimon" should be used in conjunction with headful and is used to identify |
| 43 | +# tests which require two displays connected. |
21 | 44 |
|
22 |
| -keys=2d dnd headful sound i18n intermittent printer randomness jfr cgroups |
| 45 | +keys=headful sound printer multimon \ |
| 46 | + i18n intermittent randomness jfr cgroups |
23 | 47 |
|
24 | 48 | # Tests that must run in othervm mode
|
25 | 49 | othervm.dirs=java/awt java/beans javax/accessibility javax/imageio javax/sound javax/swing javax/print \
|
|
0 commit comments