-
Notifications
You must be signed in to change notification settings - Fork 138
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
Enable/disable default test reporters via env var settings #976
Labels
Comments
christophd
changed the title
Enable/disable test reporters via env var settings
Enable/disable default test reporters via env var settings
Sep 8, 2023
Note that the dependency to <dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-autoconfigure</artifactId>
</dependency> Needs to be added to the project setup in order to accomplish this. |
good point. I would try to avoid adding the dependency. Maybe there is another way to do this without adding Spring Boot |
tschlat
pushed a commit
that referenced
this issue
Sep 16, 2023
tschlat
pushed a commit
that referenced
this issue
Sep 16, 2023
tschlat
pushed a commit
that referenced
this issue
Sep 16, 2023
tschlat
pushed a commit
that referenced
this issue
Sep 18, 2023
bbortt
added a commit
that referenced
this issue
Sep 18, 2023
…t_reporters feat(#976): Disable/Override standard Citrus reporters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User story
We should allow default test reporters to be enabled/disabled by env var settings. Once disabled the reporter should not even get initialized and log events should not be set to disabled reporters.
Additional context
Enable/disable the reporter via env var settings like HTMLReporter is doing (see HtmlReporter)
Find a way to completely remove the reporter from the list of reporters once disabled. So we do not even initialize the reporter and send log events to it once disabled.
Reporters are initialized in DefaultTestReporters. So we should make this configurable and enable/disable reporters here in order to not even initialize the disabled ones.
For Spring configuration we can use
on the reporter bean to not even initialize the bean based on the env var settings.
The text was updated successfully, but these errors were encountered: