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

Include deprecation/warning failures in JUnit logs #5839

Open
mondrake opened this issue May 19, 2024 · 0 comments
Open

Include deprecation/warning failures in JUnit logs #5839

mondrake opened this issue May 19, 2024 · 0 comments
Labels
feature/logging Issues related to logging test results type/enhancement A new idea that should be implemented

Comments

@mondrake
Copy link

When test are configured to fail in case of deprecations/warnings etc, failing tests correctly cause the testrunner to error, and deprecation/warning infromation is reported in the STDOUT (if runner is configured so), but the failures are not included in the JUnit log.

This effectively means in integrated CI environments that the test are reported as failing, but no information about the failure on the CI job, unless you look into raw logs.

Drupal completed support of PHPUnit 10 in https://www.drupal.org/project/drupal/issues/3417066, and this is visible on GitLabCI pipelines when tests trigger deprecations or warnings.

It would be good to have a flag to enable including all failures in the JUnit log.

@mondrake mondrake added the type/enhancement A new idea that should be implemented label May 19, 2024
@sebastianbergmann sebastianbergmann added the feature/logging Issues related to logging test results label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/logging Issues related to logging test results type/enhancement A new idea that should be implemented
Projects
None yet
Development

No branches or pull requests

2 participants