This repository has been archived by the owner on Dec 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 44
RedDeer logging system
jpeterka edited this page May 21, 2015
·
16 revisions
Logging in RedDeer is similar to any other logging system like log4j with some slight differences. On the one hand it is more simple and doesn't require any xml configuration. On the other hand it provides some additional logging types like dump or step.
When you want to use logger in your your class you just need define Logger from org.jboss.reddeer.common.logging package.
private final Logger log = Logger.getLogger(WorkbenchPreferenceDialog.class);
then you can log as needed in your code:
log.info("Server " + serverName + " is started");
Type | Usage |
---|---|
FATAL | fatal message mostly reporting halt state or other serious issue |
ERROR | error message for reporting any unexpected state |
DUMP | should be used after error message to provide additional information related to the error |
STEP | this should be strictly used in Test class log high-level steps that can be used to report the issue |
WARN | any warning message which indicate anything outside normal state |
INFO | information message that should provide clear information from perspective level |
DEBUG | low-level debug information usable for analyzing issues and bugs |
TRACE | low-level trace information that indicates tracking through the code |
There are these log filter switches that can be used to filter your log for message type or message level according to your needs.
Parameter | Default value | Type | Description | Source |
---|---|---|---|---|
logMessageFilter | ALL | pipe separated string | filters log messages according to settings. Possible | |
logLevel | ALL | string | filters log messages according to settings. Possible values are none,trace,debug,error,warn,info,step,error,fatal,all . Values are case insensitive |
ExecutionSettings |