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.
In my experience as a Tester, it depends on the company. In small ones, there's usually no written document about the system(s). In corporations, it might be the exact opposite, so many documents that nobody really maintains, so they capture reality only so much.
What's usually helpful to read at least to some extent (if available):
I've worked as tester for many years now but as far as I know, there is no official call for the document to help the new tester in a team to understand the company product.
Rather, in each company there is a standard way of doing things, especially if you work in big ones, for smaller ones, there almost none. As a senior QA tester, I've created documents ...