RFR: 7903752: Include duration information in JUnit-based tests
Jaikiran Pai
jpai at openjdk.org
Thu Jun 13 10:55:24 UTC 2024
On Thu, 13 Jun 2024 09:37:42 GMT, Christian Stein <cstein at openjdk.org> wrote:
> Please review this change to include duration information in JUnit-based tests.
>
> For example, see this excerpt from a `.jtr` file generated for the `JupiterTests` self-test.
>
> Before:
>
> #section:junit
> ...
> ----------System.err:(21/1306)----------
> STARTED JupiterTests::nullEmptyAndBlankStrings '[1] test('null')'
> SUCCESSFUL JupiterTests::nullEmptyAndBlankStrings '[1] test('null')'
> STARTED JupiterTests::nullEmptyAndBlankStrings '[2] test('')'
> SUCCESSFUL JupiterTests::nullEmptyAndBlankStrings '[2] test('')'
> ...
>
> After:
>
> #section:junit
> ...
> ----------System.err:(21/1306)----------
> STARTED JupiterTests::nullEmptyAndBlankStrings '[1] test('null')'
> SUCCESSFUL JupiterTests::nullEmptyAndBlankStrings '[1] test('null')' [24ms]
> STARTED JupiterTests::nullEmptyAndBlankStrings '[2] test('')'
> SUCCESSFUL JupiterTests::nullEmptyAndBlankStrings '[2] test('')' [1ms]
> ...
If you think the testng changes should be done in a separate issue that's fine with me. I just noticed that with that change to testng runner, the self tests in jtreg fail because of mismatch in the text output and those will need an update.
-------------
PR Comment: https://git.openjdk.org/jtreg/pull/206#issuecomment-2165301748
More information about the jtreg-dev
mailing list