P3
Javatest 4.1.4 (should be reproducible since jt4.0)
- write custom testsuite that would use TestSuite's loggers that forwards log messages to LogViewer (View/Logs) window. See com.sun.javatest.TestSuite#createLog(WorkDirectory, String, String)
- create logger and log there several messages with different Levels: LEVEL.SEVERE, LEVEL.WARNING, LEVEL.INFO, LEVEL.FINE
- run code. Open Log Viewer. Check that all messages are correctly mapped to 4 available "filtering" levels.
- now log some more messages with "custom" levels: LEVEL.SEVERE.intValue() - 10, LEVEL.WARNING.intValue() - 10, etc.
- run code. Open Log Viewer. You'll see that all these "custom" levels became "Debug Info" - lowest available level. While in reality (SEVERE.intValue() - 10) should be logged as "WARNING".
See javadocs for java.util.logging.Level class and logging samples to realize proper behavior.
- write custom testsuite that would use TestSuite's loggers that forwards log messages to LogViewer (View/Logs) window. See com.sun.javatest.TestSuite#createLog(WorkDirectory, String, String)
- create logger and log there several messages with different Levels: LEVEL.SEVERE, LEVEL.WARNING, LEVEL.INFO, LEVEL.FINE
- run code. Open Log Viewer. Check that all messages are correctly mapped to 4 available "filtering" levels.
- now log some more messages with "custom" levels: LEVEL.SEVERE.intValue() - 10, LEVEL.WARNING.intValue() - 10, etc.
- run code. Open Log Viewer. You'll see that all these "custom" levels became "Debug Info" - lowest available level. While in reality (SEVERE.intValue() - 10) should be logged as "WARNING".
See javadocs for java.util.logging.Level class and logging samples to realize proper behavior.