We all know the problem, we have a reporting for the unit test, which is then usually sent as a warning "Build is not running" via email.
We have a reporting for automated acceptance test, we have an overview for manual test cases. And mostly separated, and still by email.
We have the annoying topic "please read your emails" or the status in Slack. Or in other derivatives.
But here are the questions:
How did you calm down?
How did you find a suitable structure to produce a summary reporting (best to make all developers, chefs, stakeholders happy?)
Is a summary in Confluence or a connection to a wiki enough? Who guarantees that the developers even read this evaluation accordingly?