Template for an official test report
====== ====== Test Report Test Report for <system X>, <dato for rapporten>, <aktuell versjon>
\ \ Developer: \ \ The system was developed by <location utvikler>
\ \ Test: \ \ Test report was prepared by <location tester>
Type of change and complexity
Type of change:
- <As “new features”, “modification / correct mistakes” … or “subsequent testing of the emergency deployment of correction of critical errors”>
Amendment Procedure / complexity:
- <“Major / Major changes”, “Minor / Common Changes”, or “Pre-approved changes”>
Which user groups / others should be notified and how:
- <…>
Is alle changes since the last scheduled ending included (also correction of critical errors since the last change report)? <ja/nei with kommentar>
What changed and why
Reasons for change
- <som Wanted funksjonalitet, kvalitet, …>
What should be changed from a practical
- <hvor/file, Amendment 1 …>
- <hvor/file, Change 2 …>
===== ===== Risk and Impact Assessment This component: Criteria for successful / unsuccessful change
- ? Change is considered successful if
- <…>
- Change to be rolled back if the following occurs <ett/samtlige>
- <…>
- Typical symptoms of fault situations
- <…>
- Known sources of error
- <som Memory full on server, minnelekkasje, slow backend, …>
Impact on other systems (upstream and downstream)
- <system 1, effect …, any tiltak…>
- <…>
Impact on Infrastructure: Increased demands on computer resources / disk space, network, … and whether it is given the go-signal from the operating organization
- <hva, Who …>
- <…>
Deployment ===== ===== and Fallback <enter Deployment procedure (maskinstyrt/manuell) and describe exactly what that might be carried manuelt>
<Kort Pointwise description of how (makinstyrt/manuell) roll back to stable operation at possible errors in the new versjon, possibly that fallback is not feasible-begrunnes/risikovurderes>
===== ===== How tested
- <endring 1 …>
- <endring 2 …>
Critical test??
<eventuelle parts of the test which is considered critical for systemet, or unexpected testresultater>
Testers evaluation and recommendations for operational setting
<her must end with either “anbefalt driftsatt” or “tilbakelevert utvikler”>
Number of resource persons during and after operation setting
<name and seek ways for the resource person available (på place and/or per telefon)>
Excerpts of automated test log
<klippet/limt the print from the test log or link to testlogg>