-
Notifications
You must be signed in to change notification settings - Fork 44
Less verbosity in test execution #3632
Copy link
Copy link
Labels
InfrastructureChanges to the Github configurations, repository or other non-source stuffChanges to the Github configurations, repository or other non-source stuffTest cases🛠 MaintenanceCode quality and related things w/o functional changesCode quality and related things w/o functional changes
Milestone
Metadata
Metadata
Assignees
Labels
InfrastructureChanges to the Github configurations, repository or other non-source stuffChanges to the Github configurations, repository or other non-source stuffTest cases🛠 MaintenanceCode quality and related things w/o functional changesCode quality and related things w/o functional changes
Description
The verbosity during the test cases on stdout/stderr should be reduced. Currently all everything up to "DEBUG" is reported.
Logging (incl. JUnit messages) should written into a file, which is then also provided as an artifact, e.g.,
build/reports/test/<xxx>/log.txt.See the section in the JUnit documentation to achieve this (last sentence of section).
On
stdout, only summaries and faling test cases should printed.Less cluttering of stdout.