RFR: 7903519 : jtreg/jtharness is missing features for basic crash testing [v9]

[Dmitry Bessonov]

On Thu, 21 Dec 2023 12:54:22 GMT, andrlos <duke at openjdk.org> wrote:

>> this does not exactly add a crash testing option, however it allows users to define their own resultModifiers that they can force jtharness to use via advertising their resultModifier service in META-INF. I tested it with basic crashOnlyModificator and it works as intended - allows me to correctly skip and pass all the regular failures and only leaves me with crash tests as failures. Perfect for corner cases like JVM testing and such.
>> Also checked correct behavior in the logs, where the regular failure is still being reported and only the justification of the result modification is added at the bottom.
>
> andrlos has updated the pull request incrementally with one additional commit since the last revision:
> 
>   random folder usage in the unit test

For the purposes of additionally processing and changing test execution statuses you can create a subclass of `Script` (or subclass of its child class your are using) and override `::initTestDescription` method where you can use a custom `TestResult` with an overridden `::setStatus` method doing the needed transformations.

-------------

PR Comment: https://git.openjdk.org/jtharness/pull/57#issuecomment-1876892731