Here’s what I have learned over the years:<\/p>\n
Firstly the test log is not for automation folks only,<\/p>\n
Primarily for the whole product team to consume<\/p>\n
Plus automation folks would like to help it in their debugging also<\/p>\n
Keeping thwese audiences in mind, following should be a part of your log:<\/p>\n
– A good heirarchical stucture resembling the test scenarios used for regression
\n– Lots of debug information indended within the report
\n– Some info on failures we know are reported issues
\n– And finally best to have it in a centralized location, Jenkins would be best<\/p>\n
More on that here:<\/p>\n