-
Notifications
You must be signed in to change notification settings - Fork 38.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Log test aborted exceptions at INFO level in the TestContext framework
Prior to this commit, any time an aborted/skipped exception was thrown by a TestExecutionListener, the TestContextManager unconditionally logged the exception at WARN level -- or ERROR level for prepareTestInstance() callbacks. Regarding the latter, an aborted/skipped exception is certainly not an ERROR, and in general the associated log output is very verbose (including a stack trace) and not something the user should be warned about it. To improve the user experience, this commit revises TestContextManager so that it logs such exceptions at INFO level. Specifically, the following types of exceptions are considered aborted/skipped exceptions. - JUnit Jupiter: org.opentest4j.TestAbortedException - JUnit 4 org.junit.AssumptionViolatedException - TestNG: org.testng.SkipException Closes gh-31479
- Loading branch information
Showing
1 changed file
with
63 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters