In this article I’ll discuss the first step for ensuring of transparency between testing department and customer.
It is best to build the relationship in such a way that the customer sees what is happening and what he pays money for. Over time, if our relationship is transparent and we continue working with this person, this relationship is improving. This person begins trusting more and more.
Rule: Quality work + Full transparency of what is happening in the sum gives us confidence of the customer.
Comments on: "Test Summary Report + Template" (10)
what about risks? unresolved risks also be part of test summary
Generally, it depends of the situation and what information your customer wants to own. But in general, I agree with you, thank you for comment.
excelen material but I didnt see the test specification and how the test procedure is performed
I believe that the test specification should not be included in the Test Summary Report. The test specification is a separate document.
Test procedure specification: A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. [After IEEE 829].
How do you write detail summary report for Agile Method
I don’t have enough experience at Agile. So i can’t help you in this problem
Very well & to the point explained – Keep it up.
Few points could improve report such as -
- Include major unresolved defects that could impact client / management.
- Add possible recommendation to improve Software.
- Based on testing outcome, state whether current software quality meets defined software quality or not – If not – Which defects/bugs must be resolved & what needs to be done in order to meet defined quality standards. This point will impress management & client.
Thank you very much! I am very pleased
.
what about the Known issues.
The Known issues should be described in Corrective Action Plan (CAP) section.