CucumberLog4jAppender that appends to the Cucumber log
See original GitHub issueIs your feature request related to a problem? Please describe.
Some users use Log4j and want their application logs to end up in the reports.
Describe the solution you’d like
A CucumberLog4jAppender
appender class that outputs to Scenario#log
. Since a new scenario instance is created for each scenario, we would probably need a static method on the appender that can be called from a hook:
@Before
public void updateAppender(Scenario scenario) {
CucumberLog4jAppender.setScenario(scenario)
}
Additional context
This should probably be implemented in a separate sub project (/log4j
).
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Cucumber-BDD-Automation-Framework/log4j.properties
Behavior Driven Development Cucumber - Selenium based automation framework including ... Define root logger with file appender. log4j. ... Append=false.
Read more >Serenity cucumber show each step on console - Stack Overflow
Here is my log4j config. but I can not see any of steps from my .feature file showed up on console or Test.log...
Read more >Log4j with Selenium Tutorial: Download, Install, Use & Example
Log4j has three principal components · Appenders: It is used to deliver LogEvents to their destination. It decides what will happen with log...
Read more >How to use Log4j in Selenium | BrowserStack
The appender basically grabs information from the logger and writes log messages to a file or any other storage location. The following are...
Read more >Log4j Warning: “No Appenders Could Be Found for Logger”
Learn why the Log4j warning, "No appenders could be found for logger" occurs and how to resolve it, both in configuration and in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Maybe after the prototype/incubator stage is done.
Until you’ve nailed down all the problems the release frequency and general churn is going to be much higher. Not something you can do while also commiting to semver.
Given the amount of uncertainty in the exact shape of the solution, the lack of clear acceptance criteria, knowledge of, both Cucumber and logging frameworks required and general lack of clear direction this is any thing but a good first issue.
So it would benefit SmartBear, not the maintainers. Though there is some overlap. Yet at the moment it sounds like SmartBear is not interested in sponsoring this.
Perhaps you can start with a lower cost investment and write a blog post instead.
I’ve added back the
good first issue
label because it’s something I don’t think the core team is interested in implementing. I want to sign-post that this is something we would rely on the wider community to contribute.