new log level "user" for very short log files #5084
Conversation
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
…el_user_v7.0.1' into HolQue/task/log_level_user_v7.0.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dear community,
we are a team at Bosch who is since around 20 years in charge to provide test tool and infrastructure to our test departments.
We are happy to use Robot Framework.
One of the requirements we have is that tests need to run for weeks (e.g. hardware tests in climate chamber). The current Robot Framework core produces much too much log output for this purpose.
The new log level "USER" is transparent for Robot Framework users. Only if it is explicitly used and the trace level is set accordingly for the test execution, then the log output is reduced to only "USER" log entries. In "normal" log levels the new log level appears similar to already existing log outputs as per trace level.
Detailed documentation you find here:
robotframework/atest/robot/log_level/readme_log_level_test.txt
Origin of the change for this pull-reqeust ist here:
test-fullautomation#66
Changes:
new log level 'USER' introduced
amount of output reduced in debug log file and XML report file
self test in robotframework/atest/robot/log_level
documentation in robotframework/atest/robot/log_level/readme_log_level_test.txt
Based on robotframework-7.0.1.dev1-py3.9
"log level" self test extensions
IF condition and FOR loop added to log_level robot file and resource file
added log file comparison for debug log files
pattern files for log file comparison modified
documentation adapted