Missing test run log file

• Key: JDO-33
• Type: Improvement
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Michael Watzek
• Reporter: Michael Bouschen
• Component/s: ri11, tck11, tck2
• Fix Version/s: JDO 2 beta

Description

I propose write the test output into a log file in addition to what is printed on the screen. This allows to check details of any test failure while the test is still running. The TestRunner used in projects ri11, tck11 and tck20 prints the name of the test followed by the text 'ERROR' or 'FAILURE' in case the test case does not succeed. It collects any test failure details and prints it as part of the test summary at the end of the test run. These deatils get lost if teh user cancels the test run, e.g by typing ctrl-c.

Comments

[Michael Watzek]

The proposal for a fix:

The log file is created in directory "target/logs". If this directory does not exist at the time the TCK is started, then it is created. The file name pattern for the log file is "TCKLog-<currentDate>.txt". The format of <currentDate> is "yyyyMMdd-HHmmss".

You can switch off printing to a log file if you set the system property "noLogFile" to "true". In this case you'll only have console output. Otherwise, System.out and System.err are redirected to a log file and to the console.

Because the patch redirects the console output, you'll see also logging output in the log file. For this reason, we decided not to log exceptions in case of failures and/or errors using fatal/error log level. Instead, those exceptions are logged using level info. Thus, if you want to see exceptions at once with the test result, then please set the log level of the TCK to info. By default, it is set to error and you see exceptions only at the end of the TCK output after the output of all tests.

[Michael Bouschen]

Reopened to set the Fix Version/s field to JDO 2 beta.