2

Besides my manager who do I need to distribute test documentation to? E.g. master test plan and master test report.

Do I need to send the product owner/business representative, who is unfamiliar with the software testing process, a copy of those?

  • Why does your manager need a copy? My manager knows nothing about testing. He knows about how to keep me happy and coaches me to continuously improve myself. Not sure what he would do with my test documentation :) – Niels van Reijmersdal Mar 17 '17 at 15:51
2

There's so much testing documentation you could produce, your audience will vary massively... test plans, strategies, summaries, risk assessments, defect reports, etc. Not everyone needs to see everything.

Define your project team and ask them how much information they want, or how much they need.

For example, at my current client, only the Project Manager is interested in weekly progress reports in UAT, but the Test Manager wants daily progress reports.

Everywhere is different, unfortunately. There's no real standard!

1

Whomever needs it. There is no standard that you have to follow.

I always hate it if I get information I do not need. How do you figure out if people need something? Either ask them, or leave them out until they ask for it.

I would place any test documentation on a central place (e.g. a wiki) where everyone can reach it. Inform everyone once that they can find it there.

  • 1
    The "central place" is what I think is most important. I don't necessarily know who will need any test documentation/artifacts, but a day, a week, even a year later, when someone wants to know what was done, having that central place and practice around putting things there becomes very useful. – ernie Mar 17 '17 at 16:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.