-
Notifications
You must be signed in to change notification settings - Fork 13
Added more detail on TSR process, esp. around when TSRs are required #300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
||
## Reviewing the TA-TSR | ||
|
||
The tester is responsible for identifying the reviewers for the document. The reviewers for the Test Approach section and for Test Summary Report section need not be the same, but often will be. The following people will always be reviewers: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be up to the tester to identify the reviewers? If it's unclear then it seems that management should nominate the Service Owner/Product Owner responsible.
A Test Lead should review all these documents. In doing so, they are assuring the following: | ||
## When is the document modified | ||
|
||
The test approach section of the document is completed early in the project, before or at the beginning of the build phase (e.g. it could be a 'sprint 0' deliverable). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change to "early in the project, ideally before or at the beginning" ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Added more detail on TSR process, esp. around when TSRs are required
Requires review by the test community.