In my day job I need to do a lot of testing during hardware development.<\/p>\n
Over the years we developed an in my opinion quite good template for our test reports.<\/p>\n
I simplified it to simple text format just to provide the structure and required information. Design is up to you and your corporate needs such as header, footline corporation logo, font and so on.<\/p>\n
So, if you also feel the need to have a structured document for your hardware test reports, here you go:<\/p>\n
In my day job I need to do a lot of testing during hardware development. Over the years we developed an in my opinion quite good template for our test reports. I simplified it to simple text format just to provide the structure and required information. Design is up to you and your corporate needs … Continue reading Template Test Report<\/span>
\nTest-report-skeleton<\/a><\/p>\n\n= Test Report [Test Scope]\n\n== General\n\nProject Name: ____\nDevice under Test: ____ [name of PCB\/item]\nTest Subject: ____ [tested component\/functional block]\nMaturity Level: ____ [e.g. prototype, series sample]\n\nTest Operator: ____ [who performed this test]\nTest Date: ____ [when was this test done]\n\nResponsible Developer: ____ [who designed this, who can be asked]\nReviewer\/Approver: ____ [who decides that this report is good]\n\nTest Catalog: ____ [where is this test defined\/tracked]\nSchematics: ____ [where is the documentation for this PCB]\nDocument ID\/Revision: ____ [what is the number of this document for tracking]\n\n== Test Summary\n\n|| Component || Test Case || Test ID || Rating ||\n| System component A | Test Case Name 1 | Test Case Number 1 | rating |\n| System component A | Test Case Name 2 | Test Case Number 2 | rating |\n| System component B | Test Case Name 3 | Test Case Number 3 | rating |\n| System component B | Test Case Name n | Test Case Number n | rating |\n\nValues for rating: PASSED, FAILED\n additional possibilities: SKIPPED, BLOCKED, RUNNING\n\n== General Test Setup\n\n=== Device Under Test\n\nDevice Name: ____\nVersion: ____\nSer.No.: ____\n\n=== Test Equipment\n\n[What actual equipment was used performing this test.]\n\n|| Ref. || Function || Manufacturer and Type || Inventory No. ||\n| TE1 | Power Supply | Some Power Man, PSU0815 | 4711 |\n| TE2 | Multimeter | Some Meter Man, MULT007 | 4712 |\n| TE3 | Oscilloscope | Some Scope Man, OSC3004 | 4004 |\n\n=== Board Bring-Up\n\n* First action to prepare the test\n* second action to prepare the test\n* n-th action\n\n== Test Protocol\n\n=== Bug List\n|| Bug No. || Bug Description || Bugfix || Severity || Fixed in Version ||\n| 1 | Bug 1 description | short bugfix description, | bug rating | fixed version No. |\n| | link to bug tracking tool | | | |\n\nSuggestion for bug severity rating: Minor, Major, Critical\n\n=== Test Case 1\n\n==== Testing Purpose\nWhy is this test done, what does it show\/prove?\n\n==== Test Setup and Instructions\n\n* Test Conditions\n - What must be done prior to successfully executing this test.\n\n* Test Instructions\n - Step 1 [e.g. set up the output voltage of the power supply]\n - Step 2 [e.g. connect oscilloscope to the required signals]\n - Step 3 [e.g. connect additional load to circuit]\n - Step 4 [e.g. activate power supply]\n - \u2026\n\n==== Test Results\n\nTable: Test Results Test Case 1\n\n|| Description || Test Point || Expectation || Resu lt || Rating || Notes ||\n| Description Test Detail 1 | Signal 1 | Expected result | actual result | rating | optional note |\n| Description Test Detail n | Signal n | Expected result | actual result | rating | optional note |\n\n(Rating values are identical to test summary ratings.)\n\n===== Additional Test Documentation [e.g. Oscillogram Screenshots]\n\nAdditional Material\n\n==== Conclusion\n\nIs this test case passed?\nAre there observations that need to be explained?\nIf needed provide explanation why test is rated passed.\nWhat must be done to pass this test (if failed)?\n\n<\/pre>\n","protected":false},"excerpt":{"rendered":"