Open tomershadi opened 7 years ago
From an initial investigation it feels that the solution is to update to log4j 2.7 latest at this time (which is some effort since we need this upgrade in score, cloudslang repositories from log4j 1.x line
) and use a custom logging level like IMPORTANT_INFO
(with weight between INFO and WARN) to show messages at each stage: like Compiling test cases, Compiling .sl files, Running tests and Report summary messages for skipped, active, failed. We can use INFO
for rest of messages as it is now. Last piece of the puzzle is to have a CLI param for verbosity (quiet|normal|debug)
that maps quiet
value to IMPORTANT_INFO
, normal
to INFO
and debug
to DEBUG
from the log4j.properties
of the verifier module using java system properties for the values.
Another idea is to try to emulate this custom logging level on log4j 1.x line, which is a big effort if possible.
The Test Builder presents all messages of all tests to the console, even such tests that were skipped. It would be good to have a less noisy mode that hides the messages of compilation (and others) of tests that I'm not interested in.