Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] main from junit-team:main #59

Open
wants to merge 1,425 commits into
base: main
Choose a base branch
from
Open

[pull] main from junit-team:main #59

wants to merge 1,425 commits into from

Conversation

pull[bot]
Copy link

@pull pull bot commented Mar 1, 2023

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

@pull pull bot added the ⤵️ pull label Mar 1, 2023
marcphilipp and others added 29 commits November 26, 2024 09:30
Being able to attach files such as screenshots or extra log files to a 
test is useful to diagnose the outcome of tests. This PR adds an API for
Jupiter test authors to do so (`TestReporter.publishFile`) and includes
it when writing the Open Test Reporting XML output (in
`OpenTestReportGeneratingListener`) via a new method on 
`TestExecutionListener`. Moreover, it adds `OutputDirectoryProvider` to 
`EngineDiscoveryRequest` so other engines can also attach files and
write them to the same output directory and makes it available to 
`TestExecutionListener` implementations via `TestPlan`.

The default location of the XML output is changed from
`OUTPUT_DIR/junit-platform-events-*.xml` to 
`OUTPUT_DIR/open-test-report.xml`. The output directory can be made
unique by using the `{uniqueNumber}` placeholder in the
`junit.platform.reporting.output.dir` configuration parameter.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
marcphilipp and others added 30 commits January 27, 2025 17:37
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Prior to this commit, log messages for @⁠TempDir retention looked
similar to the following.

  INFO: Skipping cleanup of temp dir <path> due to cleanup mode configuration.

However, the lack of information about which @⁠TempDir declaration was
affected did not provide sufficient information to users.

To improve diagnostics, log messages for @⁠TempDir retention now
include the configured CleanupMode and describe the AnnotatedElement
(field, constructor parameter, or method parameter), as in the
following examples.

Field:

  INFO: Skipping cleanup of temp dir <path> for field TestCase.tempDir
  due to CleanupMode.NEVER.

Constructor Parameter:

  INFO: Skipping cleanup of temp dir <path> for parameter 'tempDir' in
  constructor TestCase(TestInfo, Path) due to CleanupMode.ON_SUCCESS.

Method Parameter:

  INFO: Skipping cleanup of temp dir <path> for parameter 'tempDir' in
  method test(TestInfo, Path) due to CleanupMode.ON_SUCCESS.

Closes: #4282
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Prior to JUnit Jupiter 5.12, JRE-based conditions could only rely on
predefined constants in the JRE enum. Furthermore, those constants are
only updated as long as the particular JUnit Jupiter branch is
supported. For example, once JUnit Jupiter 5.12 is released, there is
no guarantee that the JRE enum constants will be updated in the 5.11.x
branch.

Consequently, users previously did not have the ability to enable or
disable tests for Java versions released after a particular JUnit
Jupiter branch was no longer supported.

To address that, this commit introduces support for arbitrary Java
versions in the JRE enum and related condition annotations.

Users can now specify arbitrary Java versions via the `versions`
attributes in @⁠EnabledOnJre and @⁠DisabledOnJre and via the
`minVersion` and `maxVersion` attributes in @⁠EnabledForJreRange and
@⁠DisabledForJreRange.

Closes: #3930
Closes: #3931
See: #3931

Co-authored-by: Marc Philipp <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants