New answers tagged

0

A mandatory process that any software testing company should follow is to provide Sanity Report and Release Notes to the client and stakeholders post-deployment on the live environment. Sanity report should have information regarding if the list of changes is successfully deployed or not. It should also document any changes that were planned but were missed....


2

An example comes to mind: "Change request" - user wants additional changes that are not in the original scope of the app, this also includes any additional requests from the user


1

It depends on the goal of the document. This could differ per industry/company. Maybe a better question would be: "Examples of post-deployment documentation". Personally I see no need for any post-deployment documentation. Most documentation can be produced before deployment, for example, the changelog which informs users what changes where deployed. ...


Top 50 recent answers are included