Add shared file logger implementation to the test framework
See original GitHub issueWe need a common logger implementation that would always log requests/responses into files that would be added as an artifact.
There should be one file per test invocation with the path something like:
Azure.Core/HttpClientTransportTests/SomeTestNameAsync.txt
This would allow us to get rid of multiple test logger implementations and always have some logs when a test unexpectedly fails without requiring someone to instrument the code.
Issue Analytics
- State:
- Created 3 years ago
- Comments:19 (19 by maintainers)
Top Results From Across the Web
How to have one logger in every test case?
It does work but I am not sure if there is something better to have one common logger for every test case. Currently...
Read more >Set up Log4j logging in Selenium Automation Framework
Step by step process to Set up Log4j Logging in Selenium Automation framework. Set up TestNG, Data Driven, POM, Modularity, Functional Libs ...
Read more >How to implement a simple logger in C# | InfoWorld
C# logger classes The next step is to design and implement the classes. We will use three distinct classes—namely, FileLogger , DBLogger ,...
Read more >23 Slf4j - Log4j : Adding logging to your test framework
GitHub: https://github.com/PramodKumarYadav/zero Goals: 1. To add a logging interface in our test framework. 2. To add an actual logging ...
Read more >Logger in Java | Java Logging Basics with Log4j and util
This article on Logger in Java is a comprehensive guide on the Java logging API used for logging solutions while creating projects.
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
But always writing to Progress would make the output incredibly noisy. We can write to Out and a file at the same time though.
So it is true that Debug.Assert(false) would cause the Test to not be marked as Passed or Failed, but the output is still there: