Written by
- xxx
Verified by
- Hyperion TL:
- Hyperion SE:
Approved by
- xxx
REMOVE THIS TEXT
Describe:
Why this document is being prepared (Purpose).
What the document aims to do (for example who is the intended reader and what should they be able to gain from reading this document) (Objective).
What will the document cover and what will it not cover. Give a quick summary/overview as to which assembly/system you'll be talking about(Scope).
REMOVE THIS TEXT
REMOVE THIS TEXT
You can either use the text which comes with the template, write your own text or modify/tweek the text already available.
Describe:
Which types of documents are relevant to testing actvities.
What each type of documents aims to document.
When each document should be prepared.
REMOVE THIS TEXT
There are 3 main types of types of documents which relate to testing activities.
Test specification section explains:
Document should be prepared after the baseline AI&T and ~1 month before the actual test.
Test procedure serves as a detailed plan for each individual test, it contains (among other things):
Document should be prepared after the test specification and at least ~1 week before the actual test.
REMOVE THIS TEXT
Make a list of abreviations and technical vocabulary which you use in the document, then give a definition for each abbreviation, word, ...
REMOVE THIS TEXT
REMOVE THIS TEXT
Give the links to all of the documents which can give additional context to this document which includes documents which relate to the same assembly.
Example of the types of documents which you can reference.
REMOVE THIS TEXT
REMOVE THIS TEXT
Make a list of all of the requirements which you aim to verify during the test, if a requiremnt does not exist yet, contact your TL or SE. It is important to link all of the requirements which you aim verify as it will show up in the Verification Control Document which shows whether or not each document has been verified and how each requirements aims to be verified.
REMOVE THIS TEXT
REMOVE THIS TEXT
Copy paste the procedure from the Test Specification and Procedure document, then fill it out during the test.
REMOVE THIS TEXT
REMOVE THIS TEXT
Write down any notes or comments you have in regards to the procedure (for example: potential modifications for future tests)
REMOVE THIS TEXT
REMOVE THIS TEXT
Dump all of the data which you gathered up to you to decide under what format it is as long as it is accessible from this document. It can be a link, an image to a screenshot from elsewhere a markdown table with information, etc.
REMOVE THIS TEXT
REMOVE THIS TEXT
This section shall contain the analysis of test data and the relevant assessment. Basically, explain how you go from your test data to your conclusions (it can be very straight forward depending on the types of tests).
REMOVE THIS TEXT
REMOVE THIS TEXT
Take the Pass/Fail criteria from the TSP&PR document and write down wether it is a pass or a fail.
REMOVE THIS TEXT
| Criteria | Pass/Fail ? |
|---|---|
REMOVE THIS TEXT
Make a list of all of the requirements which were verified during the test.
REMOVE THIS TEXT
REMOVE THIS TEXT
Make a list of all of the requirements which you attempted to verify but failed.
REMOVE THIS TEXT
REMOVE THIS TEXT
If applicable, explain the main technical problems which arised during the test which needs to be fixed.
REMOVE THIS TEXT