Test Plan Template：测试计划模板

P09XXX Your Project NameTest Plans & Test ResultsBy: Team Member, Team Member, Team Member, Team MemberTable of contentsNote: Once you complete each of the three sections, right click on the table below and select Update Field to update the Table of Contents.)1.MSD I: WKS 8-10 PRELIMINARY TEST PLAN (3)1.1.Introduction; Overview; Summary; Purpose; History, etc. (3)1.2.Project Description; Sub-Systems/ Critical Components Being Tested (3)1.3.Approval; Guide, Sponsor (3)1.4.Test Strategy (3)1.5.Definitions; Important Terminology; Key Words (5)1.6.References (5)2.MSD II WKS 2-3: FINAL TEST PLAN (6)2.1.Data Collection Plan; Sampling Plan (6)2.2.Measurement Capability, Equipment (8)2.3.Test Conditions, Setup Instructions (8)2.4.Sponsor/Customer, Site Related, Requests / Considerations (8)2.5.Test Procedure, Work Breakdown Structure, Schedule (8)2.6.Assumptions (8)3.MSD II – WKS 3-10 DESIGN TEST VERIFICATION (9)3.1.Test Results (9)3.2.Logistics and Documentation (9)3.3.Definition of a Successful Test, Pass / Fail Criteria (9)3.4.Contingencies/ Mitigation for Preliminary or Insufficient Results (9)3.5.Analysis of Data – Design Summary (9)3.6.Conclusion or Design Summary (9)3.7.Function/ Performance Reviews (9)3.8.References (10)3.9.Appendices (10)General Notes to Teams:Please remove this page from your final test plan and test results.Not all categories in this template will apply to your project. Eliminate these categories that may not apply. Also, if there are key elements not covered, please add those items.This Test Document lists the processes and categories by which you are going to verify your final design. Fundamentally, the testing needed to prove your project meets specifications. These specifications may be categorized into features, functions and performance. MSD I Timeline and MSD II Timeline on MyCourses offers a typical example of the timing of testing. You may need to modify key milestones to apply to the specific demands of your project.The plan should be understandable by an engineer not familiar with the project.These elements can be integrated or rearranged to match project characteristics or personal/ team preferences. It may be more helpful to include traceability information (mapping of tests to specifications, customer needs, functions and features).References:/testplan.htm/library/content/c040920a.aspPLEASE DELETE THIS PAGE FROM YOUR PLANP098XX Your Project NameTest Plans & Test Results1. MSD I: WKS 8-10 PRELIMINARY TEST PLANNote to Teams: The Preliminary Test Plan is due at the completion of Senior Design 1 (Week 10) and is inclusive of both the systems specifications and specifications within and between the major sub-systems. Particular attention should be paid to the interfaces between the sub-systems since different team members may be testing each. Since the chosen technologies and associated specifications are complete at the end of Senior Design 1, the test needs should be easily comprehended and documented below.1.1. Introduction; Overview; Summary; Purpose; History, etc.Note to Team: Select the appropriate title. As an example, cut & paste information for the One Page Summary document and apply specifically to testing of the project specifications and features.1.1.1. Add here.1.2. Project Description; Sub-Systems/ Critical Components Being TestedNote to Team: If you have a high level block diagram depicting your major sub-systems, you maywant to insert here.Pick the appropriate title and or add here or remove as applicable.1.2.1. Add here.1.3. Approval; Guide, SponsorApproved by:Team Members – List team members.Guide – Professor Jane DoeSponsor – NASA, Charlie Simons1.4. Test StrategyNote to Teams: The important components of the Test Plan and later Final Test Plan are:1. What you’ll test (and what you won’t test)2. How you’ll test: equipment and materials needed, test configurations and procedures, pass/failcriteria3. Responsibilities and the approval process4. Risks and contingenciesNote to Teams: These elements can be integrated or rearranged to match project characteristics orpersonal/team preferences. It may be more helpful to include traceability information (mapping oftests to specifications and, if appropriate, to requirements and functions).1.4.1. Product Specifications, Block Diagram, and Pass/ Fail CriteriaNote to Teams: The structure of this test plan template is often consistent with thestructure utilized for engineering specifications: for each specification or feature there is adefined test method or procedure, and pass/fail criteria to demonstrate compliance with thespecification or feature. The team’s detailed Block Diagram developed during ConceptDevelopment and System Level Design is also an excellent tool to list the major interfacesto be tested.Cut & Paste the team’s specifications then add Pass/ Fail Criteria.If available, add Block Diagram indicating major inputs and outputs for final design.Each subsystem must be tested as a standalone unit by applying the possibleinput sequences and measuring the output response and confirm with theexpected response. Basically emulate the in-system inputs to conduct thisexperiment.In case of an embedded application, small test programs are run to test simplefunctions to perform at the outputs. A simple examples like switching on/off,latching, a relay, a motor ….Define each subsystem testing processes.1.4.5.3. Integration (wks 11-15)This phase of the design is most critical.There are always problems when interfacing different modules/subsystems.Fit/ Form•Summation of tolerances•Verification of calculations and assumptionsFunction•Input/ Output, Signal Processing•Synchronizing asynchronous signals•Fan-out problems•Noise problemsFor software, combine test programs you have developed for subsystem testing tocommunicate between the sub modules by adding one at a time to configureoverall system.•Check the signal integrity and timing•Check the logic levels and signal waveforms•On an oscilloscope1.4.5.4. Reliability (wks 15-20)Note: If there is a specification, such as a drop test, out of range voltage or someother form of potentially destructive testing, discuss this with your Guide andSponsor. As an example, this specification maybe waived depending upon thespecific customer needs.•Reliability is the most important characteristic•You can improve reliability by design.•However you may need special test procedure to characterize reliability.•Reliability test procedures are expensive.•Basically reliability test are conducted at elevated stress (electrical, tolerances,temperature ..) levels. Sometimes they are invasive and destructive.1.4.5.5. Customer Acceptance (wks 20-21)Finally you have to demonstrate the functionality and performance of the System tothe customer.You have to develop a Test Plan to demonstrate the critical functional in a step-by-step fashion to prove that it satisfies customer (functional) specifications.1.5. Definitions; Important Terminology; Key Words1.5.1. Add here or remove as applicable.1.6. References1.6.1. Add here or remove as applicable.2. MSD II WKS 2-3: FINAL TEST PLANIntroduction: A brief description as to how the team plans to implement their test process.Note to Teams: This Final Test Plan is due in Week 3 of Senior Design 2 and defines “how” the teamwill test and collect results. That is, list specific methodologies to verify systems specifications and any detailed sub-system specifications. This portion of the test plan may need to be revisited once testingbegins as clarify of testing needs begins.2.1. Data Collection Plan; Sampling Plan2.1.1. Data Collection StructureList of tests to be performed (indicate test # and name, test description and so on).As an example: Specification # and brief description, system component, test #, test datefield (start/stop dates may be needed), pass/fail or test result field (verification), remarksor actions needed if test failed and signoff.2.1.1.1. Component/ Device (wks 2-12)2.1.1.2. Relays2.1.1.3. Air muscles2.1.1.4. Potentiometers2.1.1.5. Controls communication with the relays2.1.1.6. Controls communication with SolidWorks2.1.1.7. Subsystem (wks 6-13)2.1.1.7.1. Elbow2.1.1.7.2. SolidWorks Model2.1.1.8. Integration (wks 11-15)2.1.1.8.1. Commands sent to and received by Solidworks2.1.1.8.2. Feedback sent from Solidworks, received by LabView2.1.1.8.3. Commands sent to and received by relay board2.1.1.8.4. Feedback sent from potentiometers and received by LabView2.1.1.8.5. Joints can support each other’s weight2.1.1.9. Reliability (wks 15-20)2.1.1.9.1. Air muscle have already been tested for stress, just not at lengthsneeded for arm control.2.1.1.9.2. Test for experimental error and workings of total system throughrepeated positioning of elbow.2.1.1.10. Customer Acceptance (wks 20-21)2.1.2. Phases of Testing(If necessary, refer to the previously documented Test 1 Phase for needs). Again, focus on how the team plans to test.2.1.2.1. Component2.1.4. Sample Size2.1.5. Reporting Problems; Corrective ActionIf the above testing cannot be performed, that will indicate a problem with one or morecomponents in the system.2.1.6. Add here or remove any other critical needs, as applicable.2.2. Measurement Capability, EquipmentIf there are measurement issues or techniques over and beyond RITs equipment, then either a,specific test devices test stands need to be designed for the purpose of testing or test waiver.2.2.1. Add here.2.3. Test Conditions, Setup Instructions2.3.1. Add here or remove as applicable.2.4. Sponsor/Customer, Site Related, Requests / Considerations2.4.1. Add here or remove as applicable.2.5. Test Procedure, Work Breakdown Structure, ScheduleNote to Team: Who is testing what? Why are you testing what you are testing? Are thereinterdependencies between subsystems (Block Diagram)? Can test equipment enable preliminary simulation of needed signals prior to integrating into the next level of completion?2.5.1. Add here or remove as applicable.2.6. AssumptionsList here including reasons why or remove as applicable.2.6.1. Add here or remove as applicable.3. MSD II – WKS 3-10 DESIGN TEST VERIFICATIONNote to Teams: Populate the templates and test processes established in Final Test Plan.These elements can be integrated or rearranged to match project characteristics or personal/teampreferences.3.1. Test Results3.1.1. Component3.1.2. Subsystem.3.1.3. Integration3.1.4. Reliability3.1.5. Customer Acceptance3.2. Logistics and DocumentationWhere are the test results being performed, logged (i.e. project notebook) and documented (i.e.excel spreadsheet)? EDGE team website structure (i.e. document names, file types, and headerlocation).3.3. Definition of a Successful Test, Pass / Fail Criteria3.4. Contingencies/ Mitigation for Preliminary or Insufficient Results3.5. Analysis of Data – Design Summary3.6. Conclusion or Design SummaryCan you explain why a particular function doesn’t work? Add here or remove howthe conclusions are to be reported or summarized (i.e. significance with confidence,pass/fail, etc.) as applicable.3.7. Function/ Performance ReviewsNote: Some teams organize reviews on a weekly bases starting in week 4 or 5 and other may wishto wait until week 10 or 11. Discuss with your Guide.3.7.1. Debriefing your Guide and Faculty ConsultantsShare test results, conclusions, any follow-on recommendations, designsummary.3.7.2. Lab Demo with your Guide and Faculty ConsultantsPerform each of the specifications and features.3.7.3. Meeting with SponsorSee Customer Acceptance above. Field Demonstration. Deliver the project.Demonstrate to the Sponsor. Customer needs met / not met.3.8. ReferencesAdd here or remove as applicable.3.8.1. Add here or remove as applicable.3.9. AppendicesAdd or remove as applicable.3.9.1. Add here or remove as applicable.。