What is a Summary in the context of software testing?

Summary in the context of software testing can mean:

• In a test report: A brief overview of the testing results, including key findings, main metrics (number of tests performed, passed, failed, blocked), identified defects (their severity, status), risks, and recommendations. It serves for a quick assessment of the product's status by stakeholders.
• In a defect report (Issue Summary / Defect Summary): A brief description of the essence of the found problem, sufficient to understand what happened without reading the full text. It should be informative and unique.
• In a test plan: A high-level description of testing objectives, scope, expected results, or key stages.
• In a project status report: A brief summary of the current testing progress, its impact on the project as a whole, and any significant issues or achievements.

The main goal of a Summary is to provide a quick and clear understanding of the essence, status, or results of testing for various audiences.