| 1 |
This is a test of the "checker shorthand" feature. |
| 2 |
See: https://checkerframework.org/manual/#shorthand-for-checkers |
| 3 |
This test is not Nullness specific. |
| 4 |
|
| 5 |
We have placed this test in this location because it has two preconditions: |
| 6 |
1) It must be run after checker.jar is created |
| 7 |
2) It must be run via CheckerMain and not via bootclasspath manipulation in the build file |
| 8 |
The normal testing methods do not require a fully built checker.jar and we did not want to force this |
| 9 |
requirement on them. Furthermore, the JUnit tests do not run through CheckerMain. This cannot be placed in |
| 10 |
the jtreg test suite because it does not run through CheckerMain. |
| 11 |
|
| 12 |
This test ensures that: |
| 13 |
a) Single checkers can be called using the shorthand notation |
| 14 |
see NullnessOnlyExpected.txt |
| 15 |
|
| 16 |
b) Multiple checkers can be called using the shorthand notation |
| 17 |
see NullnessRegexExpected.txt |
| 18 |
|
| 19 |
c) That adding a package-name in front of a checker eliminates it as a candidate for shorthand. |
| 20 |
see NullnessBadExpected.txt |
| 21 |
|
| 22 |
d) That names that aren't checkers actually lead to the usual error message for missing annotation processors |
| 23 |
even when they are of the correct form for a shorthand processor. |
| 24 |
see NonsenseExpected.txt |