Test Case Log File Generation

In addition to console logging to a file "console.log", which will contain anything logged using the "log4j" implementation, we have enabled optional test case/test step results and info logging to unique files named for the test and the date/time the test case was started. Example file name in the lib subfolder of the example_usage folder:

.../example_usage/lib/prodmanagement-2019-06-05 09-50-56.log

The java File object will populate a property in the Test entity, and can be accessed using the "Test.getConsoleLogFile()" property accessor.

To enable the writing of this file, add this key/value pair to your suite spreadsheet configuration tab.

key	value
write.test.log	true

The default behavior is to delete these files after the test suite has completed. If you want the test case level log file to remain behind at the end of the test suite run, add this key/value pair to your suite configuration tab:

key	value
leave.test.log	true

Note that leaving these values out defaults to false

• No files will be written if "write.test.log" is not present.
• Test case specific log files will be deleted if "leave.test.log" with a value of true is not present.

This functionality was added to support uploading of unique test case logs to the test case manager of your choice using the plugins manager functionality (see https://github.com/tmobile/codeless/wiki/Enabling-and-Using-The-Plugin-Manager).