The test logs provide detailed information about the execution steps, actions and responses of a test case and/or test suite. However, the logs alone cannot give a good overview of the overall result of the execution.
A reporting function is required for this purpose. After each execution of the test suite, a clear report needs to be created and published. A reusable report generator component could be used for this purpose.

Report content
The test execution report must contain a summary that provides an overview of the execution results, the system tested, and the environment in which the tests were executed, suitable for each of the stakeholders.
It is important to know which tests failed and the reasons why. To facilitate troubleshooting, it is important to know the history of test execution and who is responsible for the test (generally the person who created or last updated it). The responsible person needs to investigate the cause of the failure, report the associated issues, follow up to correct the problem(s), and verify that the correction was implemented correctly. Reporting is also used to diagnose errors in TAF components.

Publication of reports.
The report should be published for all who are interested in the execution results. It can be uploaded to a website, sent to a mailing list, or uploaded to another tool, such as a test management tool. From a practical standpoint, those interested in the test execution results are most likely to view and evaluate them if they have a subscription feature and can receive the report via email.
One way to identify problematic parts of the SUT is to keep a history of the reports so that statistics can be collected on test cases or test suites with frequent regressions.

Source: ISTQB®: CTAL Test Automation Engineer Syllabus Version 1.0