It can be called a multiple things depending on what it contains and can also be divided into separate documents.
Most commons that I have come across are:
QA Test plan standards.
one more document which isn't available readily is a stripped down version of Product demo including but not limited to requirements ...
For reporting purposes:
I find it useful to link everything in a Requirements Traceability Matrix. It gives a quick glance of how use cases get broken down into requirements, which get broken down into features (tracked by development). You can just add an additional column for automated tests + number of tests implemented. If the cell is not checked it ...
Use 'Tagging' feature of defect tracking systems like Jira/TFS to add tags like 'automated' to stories and use reporting mechanism based on 'tagging' to get desired reports of coverage assuming there is no issue with the quality of tests themselves.
Also would suggest to not to try covering each small validation in automation but focus only on the happy ...
The first question to ask yourself is if this level of traceability is necessary. For some people, maybe the answer is yes. For others, perhaps not. If you don't need traceability between story and test, you can focus on better ways to measure test coverage and correctness.
The second question to ask is how you intend to implement automation. There are ...
Don't track and link stories to tests this way. It will lead to a massive mess.
Treat your automation itself as the product.
Use the Agile principle of working software (automation in this case) over comprehensive documentation such as detailed stories and links.
Reset. Separate your tests from your stories. Create a test suite.
Use test suites to ...
An boarding document
is exactly that.
It should contain references and pointers to information such as:
End to End Tests
Product demos and videos
Links to the produce/service
Information about the various environments
Information about accounts and logins to use
The first task of any employee is to follow and update the ...
While on-boarding a new tester organizations dealing in software quality assurance services have bunch of documents. Below are the list of the same:
On boarding New Jonee Checklist.
Defect Writing Guidelines.
There can me much more in the list but the above are the important one's.