System Test Plan - The University of Texas at Arlington
Contents
1. Requirements Mapping for Data Storage Layer Hardware Tests Touch Input Unit Tests Voice Input Unit Tests Power Button Unit Tests Touch Input Processor Interfaces Hardware Input Interfaces Data Processor Interfaces Output Manager Unit Test Echo Formatter Unit Test Phone Formatter Unit Test Data Formatter Unit Tests Data Storage Unit Tests Input Layer Component Test Data Processor Layer Component Tests Presentation Layer Component Tests Data Storage Layer Component Tests Integration Tests Echo Reflection System Test Plan Echo 1 Introduction 1 1 Document Overview The System Test Plan will introduces various testing procedures that Team Reflection will follow to ensure that the Echo will perform to specifications set forth in the System Requirements Specification This document will outline the procedures team Reflection will use to all acceptance criteria set forth in previous documents In addition this document will expand on the testing guidelines set forth in the Detailed Design and will go into detail of the hardware unit component integration and system validation testing 1 2 Product Overview Echo 1s a Smart Mirror that displays applications from a user s phone to a mirror The user will be able to choose which applications to display on the mirror and enlarge the application to see it in more detail It achieves this using an ACA that communicates with and controls the Echo Echo will give a better start to th2. A0 PARE A KANAN AKA NANA ANA 47 JA BUS Report ANAN NANANALO ALA 48 10 TE SOME GUNG in o ads 49 ka PND OY AA AA AA 50 System Test Plan Version 1 0 4 Reflection System Test Plan Echo Document Revision History Revision Revision Date Description Rationale Number October 5 2014 STP First Draft Initial draft for STP October 16 2014 STP After Review Baseline Submission System Test Plan Version 1 0 5 Reflection System Test Plan Echo List of Figures FIGURE PAGE Proure General Syste BA AA 9 Figure 2 1 dren bevel Layer Den mitiOns ciclos 15 Pisure 2 2 Architecture Desi em DIR STA n Eke NAAN E ee N 17 His re 2 5 Detail Desi e e e xwar w 19 Proure oL Relational Pagamutan 24 System Test Plan Version 1 0 6 Reflection System Test Plan TABLE Table 2 1 Table 2 2 Table 2 3 Table 2 4 Table 2 5 Table 3 1 Table 3 2 Table 3 3 Table 3 4 Table 3 5 Table 3 6 Table 3 7 Table 3 8 Table 3 9 Table 3 10 Table 3 11 Table 3 12 Table 3 13 Table 3 14 Table 3 15 Table 3 16 Table 3 17 Table 4 1 Risk Table Table 8 1 Hardware Pass Fall Criteria Table 8 2 Unit Tests Pass Fail Criteria Table 8 3 Component Test Pass Fail Criteria Table 10 1 System Testing Schedule System Test Plan Version 1 0 List of Tables Architectural Requirements Mapping Table Requirements Mapping For Input Layer Requirements mapping for Data Processing Layer Requirements mapping for Presentation Layer
3. Data Processing Layer Android TV Box Display Formatter gt phone Formatter Presentation Layer Speaker y Data Storage Layer Figure 3 1 Relational Diagram System Test Plan Version 1 0 24 Reflection System Test Plan 3 1 Hardware Tests Test Expected Echo Requirements Component Output Satisfied HW1 Microphone The user speaks The microphone Test the 3 4 3 10 into the accepts and microphones microphone records the output by words the user checking the says output log of the microphone and ensure it is recording the words being said HW2 Speaker The user brings The system Test the speakers 3 3 3 6 up music on the should play the by telling the Echo Echo system music through system to play the speakers music and ensure 1t plays the music appropriately HW3 Screen The user will The system will Test the screen by 3 2 3 9 3 11 press the power turn the screen pressing the power button on the on and display button on the side Echo system the home screen of the Echo system of the ACA to ensure it turns on and off HW4 Android TV The user will The system will Test the screen by 3 1 Box press the power turn the pressing the power button on the Android TV button on the Echo Echo system box on and start System to ensure it the ACA turns on and off
4. System Test Plan Echo 8 Item Pass Fail Criteria The following section will determine the criterion needed for the module test to be accepted as passing or failing Only the modules that have passed will be accepted into the final Echo product the failed modules will be corrected in order to be acceptable 8 1 Hardware Tests Test ID Component Pass Criteria _ Fail Criteria HW Microphone Correctly intakes the Does not intake the voice commands and voice commands or sends it to the system sends wrong PI commands HW2 Speaker Correctly outputs the Does not output audio audio HW3 Screen It turns on o power It does not turn on or connection and display the ACA displays the ACA HW4 Android TV Box It turn on once It does not turn onor connected to power show the installed and to the screen and apps or does not let shows all the Apps the team install more It lets the user install apps more applications from play store Table 8 1 Hardware Pass Fail Criteria 8 2 Units Tests Test ID Pass Criteria Fail Criteria UTH Be able to detect keyboard Fails to detect keyboard input or input and touch input by touch input by screen tap and slide screen tap or slide eel UTR Be able to create list of apps Fail to create a list of apps from the from the selections m
5. Providing details on the system s overall components and structure This is a high level overview and the subsections following need to be thoroughly tested as to show the system s architecture 1s working properly 2 2 1 Layer Overview Input Layer Data Processing Layer Presentation Data Storage Layer Layer Figure 2 1 High Level Layer Definitions Input Layer The purpose of the Input Layer is to accept input from the user The layer accepts input from the user through the phone s touch screen This will serve as a secondary source of input from the user to the system Information from the Android Control Application ACA is sent to this layer where it is initially processed and then formatted Once the data has been formatted it is passed to the next layer to be further processed The Hardware Sub Layer accepts data from the mirror microphone and the power button This will serve as the main source of input from the user into the system This layer will listen for the key command words spoken by the user The information will go through an event handler in order to distinguish what actions need to be taken with the given input every word after the key word Echo is collected After the speech recognition has been formatted 1t 1s converted to strings to be sent out for processing System Test Plan Version 1 0 15 Reflection System Test Plan Echo Data Processing Layer The purpose of the Data Processing Layer is to
6. Table 3 1 Hardware Tests System Test Plan Version 1 0 25 Reflection SZ System Test Plan Unit Tests 3 2 1 Module GUI Listener User touch Event Handler Application Check lists sync button status screen input Touch Input Subsystem Expected Output Identified touch screen action List of selected applications and a sync button activation call Test the GUI listener by typing tapping or sliding on the screen ensuring 1t correctly identifies each action Test the Event Handler by selecting applications from the home screen list and Echo Priority pressing the sync button ensuring the correct applications are displayed on the screen Priority Reflection Table 3 2 Touch Input Unit Tests 3 2 2 Voice Input Subsystem Module Input Expected Output Speech Recognition activation signal and audio beep to confirm Echo was recognized Tokenized voice input in the form of a text string matching users vocal command Echo Activation Service Test the Echo Activation Service by saying the word Echo while the system 1S On Test after Echo has been said by speaking any command User says Echo Speech Recognizer User says command Table 3 3 Voice Input Unit Tests System Test Plan Version 1 0 26 System Test Plan Echo 3 2 3 Power Button Subsystem Test Module Input Expected Priority ID Output User presses the If t
7. created incorrectly The voice commands are not being acted upon or the incorrect actions are being performed on applications It does not make an Android system call The subsystem will not display application Interface on the screen Table 8 3 Component Test Pass Fail Criteria System Test Plan Version 1 0 46 Reflection System Test Plan Echo 9 Test Deliverable This section will list what is to be delivered by this test plan that is system test plan test cases test report and Incident Bug Problem Reports IRs Under each subsection we will list the parts that go with them 9 1 System Test Plan The System Test Plan will provide an overview of what will be tested how it will be tested and the pass fail criteria for each test depending on the expected input outcome 9 2 Test Cases Fach test case will consist of the following section Test ID The ID corresponding to the test case Test Item The name of the subsystem module to test Purpose Reasoning for the test Test Description a short summary of what will be done as part of the test Input Input that will be supplied to the test item Expected Results Expected result of the test Priority The priority of the test low medium high Critical 9 3 Test Report Fach of the test report will consist of the following section e Test ID The ID corresponding to the test case e Test Date The date when the test will be performed e Tester The name
8. that may affect testing and or the test outcome It will also show impact assessment and management plan as it relates to these risks 4 2 Risk Table Risk Description ID Impact Severity Mitigation R1 Trickle down It will make it very hard to Medium To make sure the interfacing error detect where the fault is object requested are the from same and catch the error early by doing unit testing component testing and finally integrated test R2 Failure of This cannot be fixed by us High We are having the third external the developers and it can also party application to work software or cause the test to give out independent of the rest of third party undesired output the system after they are application called R3 Hardware This may cause the High We are testing the hardware Failure component test to not separately to see 1f they produce any outcome at all work with other applications or produce undesired before we test 1t will our outcome system R4 Server This may cause settings not Medium We will check if the server Connection be sent to the echo from the connection before we send error phone the settings Table 4 1 Risk Table System Test Plan Version 1 0 36 Reflection System Test Plan Echo 5 Features not to be tested This section details what requirements will not be tested and why Largely most requirements not
9. with Android OS Processor call to open ACA and we will verify 1f it opens the App on boot up UDP7 Application Request Application We will provide the Critical Request Data module with Voice Processor Command in form of String and verify if performs the requested action UDP8 Application AppMessa InterfaceReq We will provide the Critical Request ge Object uest Object Module with AppMessage Processor Next Page object and verify the module returns the data requested Table 3 7 Data Processor Interfaces 3 2 7 Output Manager TestID Model Input Excepted Test Description Priority Results UOM1 Dispatcher Application Application We will provide the method High data interface with application interface and verify 1f 1t displays 1t on screen Table 3 8 Output Manager Unit Test System Test Plan Version 1 0 29 Reflection System Test Plan Echo 3 2 8 Echo Formatter TestID Model Input Excepted Results Test Description Priority UEF1 Speaker Audio File Sound data We will provide the High Formatter path method with a test audio path and see 1f 1t will play the audio file UEF2 Display Application Display data We will provide the Formatter data to method with a test display string of display data and see 1f it will correctly display data passed Table 3 9 Echo Formatter Unit Test 3 2 9 Phone Formatter Test Model Input Exce
10. 5 14 Processor Testing System Boot Up Testing 11 5 14 11 15 14 Data Formatter Testing 11 5 14 11 15 14 Data Storage Testing 11 5 14 11 15 14 Dispatcher Testing 11 5 14 11 15 14 Display Formatter Testing 11 5 14 11 15 14 Speaker Formatter Testing 11 5 14 11 15 14 Component Testing 11 15 14 11 20 14 Touch Input Testing 11 15 14 11 30 14 Voice Input Testing 11 15 14 11 30 14 Power Input Testing 11 15 14 11 30 14 Touch Input Processor 11 15 14 11 30 14 Testing Hardware Input Processor 11 15 14 11 30 14 Testing Data Processor Testing 11 15 14 11 30 14 Output Manager Testing 11 15 14 11 30 14 Phone Formatter Testing 11 15 14 11 30 14 Echo Formatter Testing 11 15 14 11 30 14 Data Formatter Testing 11 15 14 11 30 14 Data Storage Testing 11 15 14 11 30 14 Integration Testing 11 20 14 11 30 14 Input Layer Testing 11 20 14 11 30 14 Data Processing Layer 11 20 14 11 30 14 Testing Presentation Testing 11 20 14 11 30 14 Data Storage Testing 11 20 14 11 30 14 Table 10 1 System Testing Schedule Reflection System Test Plan Echo 11 Approval Name Role Signature Mike O Dell Project Supervisor J Project Sponsor i Team Leader Team Member Tanmay Kumar Patel Team Member Aisha Kulindwa Team Member Jacob Fisher Team Member 5555555 System Test Plan Version 1 0 50 Reflection
11. Criteria Pass Criteria Input from ACA is recognized and processed The command word is recognized when spoken and voice commands are recognized The power button press is recognized and TV box is turned on System Test Plan 8 3 Component Tests Test ID Subsystems CTI Touch Input CVCI2 Voice Command Input CPB3 Power Button Input CTIP1 Touch Input Processor CHIP2 Hardware Input Processor CDP3 Data Processor CDP4 Data Processor CDPS Data Processor COMI Output Manager The JSON object is made and transferred to the Server on Echo correctly The voice commands are parsed and validated JSON object 1s retrieved and parsed and tables of relevant information are created for storage The voice commands are acted upon and proper action 1s taken upon the applications The System makes an Android System call after the startup button 1s pressed The subsystem displays the Application interfaces on the Screen correctly Input from ACA is not recognized or not processed The command word 1s not recognized by the subsystem or the voice commands are not being processed The power button input is not recognized and the TV box doesn t turn on The JSON object is not made or the transfer does not happen correctly The voice commands are not parsed properly or not validated correctly JSON object 1s not retrieved or the proper tables are not being created or are
12. Department of Computer Science and Engineering The University of Texas at Arlington Reflection Echo Voice Controlled Interactive Mirror Team Members Jacob Fisher Sumeet Kaur Aisha Kulindwa Sean Nesburg Tanmaykumar Patel Last Updated October 16 2014 System Test Plan Echo Table of Contents t os 06 Nel NA 8 Lal DOCUMENOVETVIEN rca titre NANA E 8 L2 ELOdUCCO VEN uta iii iii 8 ba A k Wer N Ab N W RA K r AK R Net 8 Dao TES REECE ira 10 Zuka System Requirements Special NANAKIT E k A 4na k kA 10 ZAC USOmer REQUNEMEN a 10 Z2 Pac kos me Regae mei acu 11 21 PETLOEMANCE REUTERS a EAE 12 ZAS EY REGUIFCMICING ai AAA A AASA 12 2 1 5 Maintenance and Support Requirements iii ANAN 13 ZLO Other Reduir MoNS NA TANG AJ AN 14 Zas Architectural Desten S Dec lid lO Dl La AGA AA 15 22 LAY OVEN Waa O OO E PEO BANA 15 222 SUD EMU CIS is 17 2253 a A O AA A AN 18 2 5 Detaled Deston o Pec CaO Mn sce ete cesta nti ANA AA Aa 19 2 51 MIO CINE CV ELV A A eal met Gate 19 2 3 2 Requirements lele a aaa dica 20 De CSU AUC INS A o Pe 24 Sle N AA Meas eee 25 P DOET NAA AA 26 335 Component TO ANG ANA NA AA AA AA 32 DAL NA AA 35 AG NA A a a 36 Al ND K la E Wii 36 AG ol JR E e n Da Da n e 36 3 Features NOLO DE tetona 37 System Test Plan Version 1 0 2 Reflection System Test Plan Echo SL Customer Requirements laa 37 2 Performance Requiiementsiousdn idad 37 Side Backagime Requires 37 Fealurestorbe Le
13. Reflection System Test Plan Echo 3 7 Bluetooth Phone connects to mirror via Bluetooth All the 1 Critical Connectivity data transfer happens via Bluetooth 3 8 Pill Reminder The Android application shall come with an 4 Low Applet applet that will let the user set reminders for pills and will allow the user to upload pictures of the pills The user will be able to see the directions as well as the pictures of the pills they need to take that day 3 9 Resolution and Echo will have a high enough resolution and be 2 High Brightness bright enough so that the user will be able to see all information displayed clearly 3 10 Microphone Echo will have a microphone built onto it This 1 Critical will allow the user to interact with the ACA hands free 3 11 Power Button Echo will have an external power button to allow 1 Critical the user to conserve energy and to power down the system 1f desired Table 2 1 Customer Requirements 2 1 2 Packaging Requirements SRS No Requirement Description Priority 4 1 Mirror Housing The components of Echo will be attached to the 2 High inside of the wooden housing to secure them in place The housing will prevent any of the components from being exposed to the user The housing will be rectangular in shape wooden box The housing will also have mount for the phone The housing will keep moisture from entering Echo 4 2 Mirror Size Echo will be no larger than 44 x 24 x 8 3 Mo
14. accept data that has been gathered through the input layers and to trigger events that correspond with the needs of the user This layer contains components to analyze the data that is being received from the other layers After the data has been analyzed it is sent to the app command processor where the command is processed into a request and sent to the Internet and database The appropriate action will be generated and sent to the presentation layer This layer also contains a component to deal with API requests to the Internet as well as their responses Presentation Layer The purpose of the Presentation Layer 1s to present information to the user This could be via LCD Screen the speakers or the Android Control application on the phone Data to be output is sent from the Data Processing Layer to the Presentation Layer and is then routed to the correct output formatter based on the data received After the data has been formatted to the correct medium 1t is presented to the user via that channel Data Storage Layer The purpose of the Data Storage Layer 1s to store or retrieve data for the Data Processing Layer The components inside this layer will facilitate saving or retrieving data as necessary Data can flow in or out of this layer Data flowing in from the Data Processing Layer will be converted to a more suitable format for being saved on the file system Data flowing out will be converted from 1ts file format to a data structure tha
15. ach The team will speak voice commands into the microphone to test that it is able to take in audio input clearly and correctly Power Button Description Echo will an external power button to allow the user to conserve energy and to power down and power up the system Test Approach The team will test this by pushing the button on the Echo and see 1f turns off the system and then push it again to see 1f 1t turns the system back on Packaging Requirement 6 2 1 6 2 2 Mirror Housing Description The components of Echo will be attached to the inside of the wooden housing to secure them in place The housing will prevent any of the components from being exposed to the user Test Approach The components will be tested to make sure that they are securely attached to the insides of the Echo housing The team will see that none of the hardware that is used will be exposed to the user Mirror Size Description Echo will be no larger than 44 x 24 x 8 Test Approach The team will measure that the housing is same or less than the measurements shown above System Test Plan Version 1 0 39 Reflection System Test Plan Echo 6 3 6 4 6 2 3 6 2 4 Mirror Weight Description The weight of Echo will not exceed 501lbs Test Approach This will be tested by measuring the weight of Echo Power Cable Description The cable will be used as the source of power for the Echo The power Cable can be modular Test Approac
16. ade by selection or create incorrect lists the user from UVIl Be able to recognize the Fail to recognize the command command word Echo from word or activate on a wrong the user command word j UVI2 Be able to tokenize the voice Fail to tokenize the voice commands into corresponding commands or tokenize the voice strings commands incorrectly into string System Test Plan Version 1 0 44 Reflection System Test Plan UPB1 UTIP1 UTIP2 UHIP1 UHIP2 UDP1 UDP2 UDP3 UDP4 UDP3 UDP6 UDP7 UDPS UOMI1 UOM2 Be able to turn on the system when the system is off and vice versa Be able to create a JSON object from a list of applications correctly Be able to display the list of selected applications on phone screen Be able to parse the string and remove all of the words that are not command words Be able to turn on the ACA on the echo on system boot up Be able to connect and send JSON object over the W1 Fi Be able to parse the JSON object and retrieve package info for the applications found in JSON object Be able to show the icons of the favorite s app to the user on Echo Be able to send the string command to application processor if the command is valid for the situation Be able to discard the string commands if they are invalid for the situation Be able to turn on the ACA on the echo on system boot up Be able to perform the requested a
17. all include adequate anchors and 1 Critical screws such that it can be safely secured to the wall 6 2 Packaging Safety The system shall be packaged such that there 1 Critical will be no exposed circuitry to the user 6 3 Heat Dissipation The system shall be able to dissipate the heat 2 High generated by the components of the system Table 2 4 Safety Requirements System Test Plan Version 1 0 12 Reflection System Test Plan Echo 2 1 5 Maintenance and Support Requirements SRS No 7 1 72 7 3 7 4 75 7 6 System Test Plan Version 1 0 Requirement User Manual Troubleshooting Guide Application Updates System Software Priority 1 Critical Description The user manual will include step by step instructions on how to initially install the system as well as the accompanying mobile application It will also include directions on how to use all of the features of the system The system will come with a troubleshooting 1 Critical guide to identify some of the problems and recommend possible solutions to both hardware and software aspects of the system The Android application accompanying Echo 2 High will receive updates to resolve bugs The instructions will be included in the user manual Echo system will receive updates directly via the 3 Moderate Updates accompanying Android application to resolve bugs The instructions will be included in the user manual Hard
18. being tested are simply those not being implemented but to clarify each requirement will explain why it is not being tested 5 1 Customer Requirements 5 1 1 Pill Reminder Applet Description The Android application shall come with an applet that will let the user set reminders for pills and will allow the user to upload pictures of the pills The user will be able to see the directions as well as the pictures of the pills they need to take that day Reason The pill reminder applet will not be implemented in the final product 5 2 Performance Requirements 5 2 1 Smart Phone to Mirror Synchronization Delay Description There will be a small delay of 1 to 2 seconds in the reaction of the screen synchronizing with the phone Reason The synchronization action will not be taking place as frequently as other integral systems The only thing when it comes to synchronizing the mirror and smart phone being tested is whether or not it is actually synchronizing 5 2 2 Internet API Interface Latency Description The apps displayed on the mirror will be retrieving real time data from multiple websites There will be a standard web service delay of on average 50 200ms delay in data query and display Reason This will be irrelevant to test as internet service will differ depending on where the system is installed 5 3 Packaging Requirements 5 3 1 User Manual Description There will be user manual provided with the system with instal
19. ction System Test Plan 2 3 2 Requirements Traceability Input Layer Requirement Number 3 4 3 3 3 3 3 1 s2 3 5 6 7 8 9 Requirement GUI Event Echo Speech Name Listener Handler Activation Recognizer Service Android Control Application Voice Recognition How To Application Speakers Mounted on Echo Server Connectivity Resolution and Brightness Power Button Pill Reminder Applet Table 2 2 Requirements Mapping For Input Layer System Test Plan Version 1 0 20 Echo System Power Reflection System Test Plan Echo Data Processing Layer Requirement Requirement Request Command Command Request App Number Name Processor Validation Processor Handler Request Processor Android Control Application Display Multiple Application Icons Switch between Applications Voice Recognition How To Application Speakers Mounted on Echo a EN Server Connectivity Resolution and zz i E EZ ZE O A RE 10 Power Button Button E 11 Ei Reminder Applet Table 2 3 Requirements mapping for Data Processing Layer System Test Plan Version 1 0 21 Reflection System Test Plan Echo Presentation Layer Number Formatter Formatter Android M Control Application Display Multiple Application Icons Voice Recognition How To Application Requirement Requirement Name Dispatcher Phone Speaker Echo Formatter Speakers Mounted on Echo Resolution and B
20. ction based on string command Be able to display the requested application data Be able to display information on Echo correctly Be able to output audio on speakers properly Echo Fail to turn on the system when the system is off or fail to turn off the system when the system is on Fail to create a JSON object from the list of applications or create JSON object incorrectly Fail to display the list of applications or display incorrect icons for applications Fail to parse the string correctly by either removing command words or not removing words that are not commands Fail to turn on the ACA on boot up Fail to connect or fail to send the JSON object correctly over the Wi Fi Fail to parse the JSON object correctly or fail to retrieve the package information correctly Fail to show the icons of the favorite s app to the user Fail to send the string command or send the string command even if the commands aren t valid for the situation Fail to discard the commands if they are invalid for the situation or discard the commands even if they are valid Fail to turn on the ACA on boot up Fail to perform the requested action based on the string command Fail to display the requested application data Fail to display information on Echo correctly Fail to output audio speakers properly Table 8 2 Unit Tests Pass Fail Criteria System Test Plan Version 1 0 45 Reflection Echo Fail
21. derate 4 3 Mirror Weight The weight of Echo will not exceed 50 lbs 3 Moderate 4 4 Power Cable The cable will be used as the source of power for 1 Critical the Echo The power cable can be modular Table 2 2 Packaging Requirements System Test Plan Version 1 0 11 Reflection System Test Plan 2 1 3 Performance Requirements Echo Requirement Description Priority 5 1 Smart Phone to There will be a small delay of 1 to 2 seconds in the 3 Moderate Mirror reaction of the screen synchronizing with the phone Synchronization Delay 5 2 Smart Phone There will exist a small delay of up to a second 2 High Control Latency between the input controls and the corresponding action of the mirror due to processing delay 5 Internet API The apps displayed on the mirror will be retrieving 4 Low Interface Latency real time data from multiple websites There will be a standard web service delay of on average 50 200ms delay in data query and display 5 4 Speaker Quality Echo speakers must have high quality so that the user 2 High can clearly hear the system 5 5 Microphone The microphone mounted on Echo must be of high 2 High Quality quality such that the voice commands are correctly interpreted by the system Table 2 3 Performance Requirements 2 1 4 Safety Requirements Requirement Description Priority 6 1 Installation The system sh
22. display for the screen The mirror itself will be a mountable box that will keep all components inside while keeping moisture out and allowing sound to come in and heat to dissipate The ACA will be the main interface between the applications and the user It will take the commands both voice and touch and use it to interact with the applications The ACA will also store the list of videos for the How To application System Test Plan Version 1 0 8 Reflection System Test Plan Echo display visual sound voice ee a touch Data Data request Data Figure 1 1 General System Diagram System Test Plan Version 1 0 9 Reflection System Test Plan Echo 2 Test References The System Test Plan will be based on previous documents produced by team Reflection These documents are the System Requirements Specification SRS Architecture Design Specification ADS and the Detailed Design Specification DDS The following sections and subsections will define for the reader our testing approach and will help the reader understand our system better Lolo System Requirements Specification The SRS is the original requirements documentation which were created by the members of team Reflection and the sponsor Dr Becker This document introduced the product specified in detail what was needed for the product to be considered complete and the purpose of the product These requirements will be covered in th
23. e day The few minutes that you spend in front of the mirror looking at your reflection could be used more productively While brushing your teeth you can inquire about weather social updates calendar events emails or even listen to music Echo 1s designed for the average consumer who wishes to view information more easily than on their phone The ACA will allow the user to select various apps that are on their Android phone The selected apps will be displayed on the mirror and will allow the user to see updated information similar to normal locked screen updates An example is the busy student They wake up go to the bathroom to do their morning rituals and they can see what their friends posted on Facebook figure out how to get that perfect look for their presentation play some upbeat music and see what the weather 1s like all while brushing their teeth and getting ready for the day 1 3 Project Description Echo will consist of two major components the mirror and the ACA The mirror will hold the display unit speakers microphone and a motherboard The display unit will be a LCD screen that will display user s requests The speakers will send sound from the music application or from the How To application to the user The microphone will allow the user to interact with the ACA using voice commands The motherboard will analyze the voice commands and send it to the ACA and receive information from the ACA and make it into a
24. f the array list gets converted into the JSON object We will provide the subsystem with voice commands and verify if the commands are processed Echo Priority Critical Critical correctly We will also test if on startup the system makes an android system call We will test and verify that the subsystem takes in the JSON object performs the conversion and search and displays the application icons on the screen We will test this subsystem Critical by sending a string command like open calendar and verify if it opens the application and displays it on the screen High We will test this subsystem High by providing startup command and verify if the subsystem opens the ACA On startup Table 3 14 Data Processor Layer Component Tests System Test Plan Version 1 0 33 Reflection System Test Plan Echo 3 3 3 Presentation Layer Test Subsystem Input Excepted Test Method Priority ID Results CPL1 Output Application Application We will provide the method High Manager data interface with application interface and verify if it displays it on screen CPL3 Echo String of Display data We will provide the High Formatter data to subsystem with string of data display and expect it to display the formatted data passed CPL4 Echo String of Sound data We will provide the High Formatter audio file subsystem with a string of file path path and see if the right file Wi
25. h The team will use the power cable by plugging it into the wall outlet and test that it supplies the power to the system by turning the system on Performance Requirement 6 3 1 Voice Command Recognition Latency Description There will exists a small delay up to a second between the input of the voice command and the action that is performed based on the voice command Test Approach The team will test using a stop watch that the delay between the input of the voice command and action being performed by Echo is less than 1 second Safety Requirement 6 4 1 6 4 2 6 4 3 Installation Description The system shall include adequate anchors and screws such that it can be safely secured to the wall Test Approach The team will install the Echo onto a wall to test that is it securely mounted Packaging Safety Description The system shall be packaged such that there will be no exposed circuitry to the user Test Approach The team will test this requirement by testing that there 1s no exposed circuitry to the user Heat Dissipation Description The system shall be able to dissipate the heat generated by the components of the system Testing Approach The team will test this by measuring the heat inside the Echo and determine that it s under the recommended temperature System Test Plan Version 1 0 40 Reflection System Test Plan Echo 7 Testing Approaches The following section will describe the overall approach and s
26. he system is Test the power Critical external system off the screen button subsystem power button turns on and the by pressing the ACA starts power button ensuring the system turns on and off Table 3 4 Power Button Unit Tests 3 2 4 Touch Input Processor Subsystem Module Test Method Priority Request List of JSON Object We will provide the Critical Processor Applications module with a List of Applications and verify 1f the module outputs a JSON object Request List of App Icons We will provide the Medium Processor Applications module with a list of selected applications and verify if it displays the application icons on the next screen on the phone Table 3 5 Touch Input Processor Interfaces System Test Plan Version 1 0 21 Reflection System Test Plan 3 2 5 Hardware Input Processor Subsystem ID UHIP1 Module Command Validator Input String Output Parsed String Test Method We will provide the Module with a string command and verify if is parses the string by picking the key commands Echo Priority Critical UHIP2 System Boot up Digital Signal lt Android OS call We will provide the Module with a digital signal and verify if it starts ACA on Boot up Table 3 6 Hardware Input Interfaces 3 2 6 Data Processor Subsystem ID UDP1 Module Serve
27. is subsection 2 1 1 Customer Requirements Requirement Description Priority 3 1 Android Control It is an Android application that is used to 1 Critical Application control Echo system It shall interact with other applications on the user s phone and fetch data from those applications to display on the mirror 3 2 Display Multiple The Android M Application and the mirror shall 1 Critical Application Icons display multiple application icons on the main opening screen For example Facebook Weather Calendar Clock Music and How To app The user can choose one of the available applications to open and display the large interface of the application on the mirror 3 3 Switch between The Android Application shall allow user to 1 Critical Applications switch between the Android applications by either using the touch screen from phone or using voice command 3 4 Voice The user can use voice commands to interact 2 High Recognition with Echo 3 5 How To The Android application associated with Echo 1 Critical Application will have an applet that allows the user to watch How to videos such as how to tie a tie This will allow the user to mimic the video while being able to see him or herself All of the how to videos will be preselected 3 6 Speakers Echo shall have speakers mounted on to it User 1 Critical Mounted on Echo shall be able to hear audio for videos and music System Test Plan Version 1 0 10
28. lation instructions Reason This feature will not be tested as it will be included in the final product System Test Plan Version 1 0 37 Reflection System Test Plan Echo 6 Features to Be Tested The following section will describe all the features based on the requirements stated in the System Requirement Specifications that need to be tested 6 1 Customer Requirements 6 1 1 Android Control Application Description Echo shall have an Android Control Application that 1s associated with it It Will be used to control the Echo system by allowing the user to configure the applications that he she wishes to display on Echo Test Approach The application ACA will be installed on an Android based device and it will be used to connect with the Echo Applications will be selected on ACA and then the ACA will be synced with the Echo to transfer the settings and determine 1f the user configurations have been correctly set Display Multiple Application Description Echo will be able to display multiple applications on its Home Screen The user can choose one of the available application to open and display the large interface of the application on the mirror Test Approach The team will test to see 1f multiple applications are being displayed on the home screen of Echo Also the team will open each of the applications and see 1f it is being displayed 1n its full version Switch between Applications Description The Echo will al
29. ll be played CPL5 Phone String of Display data We will provide the High Formatter data to subsystem with string of data display and expect it to display the formatted data passed Table 3 15 Presentation Layer Component Tests 3 3 4 Data Storage Layer Test ID Subsystem Input Excepted Results Test Method Priority We will send data into the sub system and see 1f the data is stored into the database correctly We will see if the sub system will package the correct information together and send it correctly CDSL1 Data Storage Manager String String to the database High CDSL2 Data Formatter Strings Strings to Array List High Table 3 16 Data Storage Layer Component Tests System Test Plan Version 1 0 34 Reflection System Test Plan 3 4 Integration Tests Test ID Layer Test Method Echo Priority 11 Input Layer User interaction Application The ACA will be tested Critical with ACA Selection list in through a variety of touch the form ofan screen inputs including arrayList sliding across and tapping the screen I2 Input Layer User voice input Parsed voice Testing of the Echo systems Critical command voice input shall be through a string variet
30. low the user to switch between the applications that they are currently using Test Approach The team will test Echo to see 1f it is allowing a user to switch from the current applications to a different application that is available to them Voice Recognition Description The user will be able to interact with Echo using voice commands Test Approach The team will use pre selected voice commands to interact with the Echo 1n order to test this requirement How To Application Description Echo will have an application that will allow the user to watch pre selected How To videos that are hosted on YouTube System Test Plan Version 1 0 38 Reflection System Test Plan Echo 6 2 6 1 6 6 1 7 6 1 8 Test Approach The team will test to see 1f Echo has the how to application on it if it is on Echo the team will open the How To application and play one of the pre selected how to videos Afterwards the team will test the functionality of How To by closing the video and opening up another video from the pre selected video Speakers Mounted on Echo Description Echo will have speakers mounted on to it User will be able to hear audio for videos and music Test Approach The team will play music or a video on the Echo to see 1f they can hear any audio coming out of the speakers Microphone Description Echo will have a microphone built onto 1t This will allow the user to interact with the ACA using voice commands Test Appro
31. o Subsystem Input Expected Output Priority CIL1 Touch Phone touch Touch screen Test the touchinput Critical Input screen commands subsystem by testing Input application various touch screen selection lists and inputs on the screen sync command such as tapping and sliding ensuring the correct buttons and commands are registered CIL2 Voice User voice System command Test the voice Critical Command input in the form of a text command subsystem string by activating it with the Echo keyword then saying a system command CIL3 Power Pressing the The Echo screen Test the power Critical Button external and Android TV button subsystem by power box both turn on pressing the power button button and ensuring the system turns on Table 3 13 Input Layer Component Test System Test Plan Version 1 0 32 Reflection System Test Plan 3 3 2 Data Processing Layer ID Subsystem Input CTIP1 Touch Input List of Processor Applications CHIP2 Hardware String voice Input or system Processor startup command CDP3 Data JSON object Processor CDP4 Data String voice Processor command CDP5 Data Android Processor system call Output JSON Object String or Android system call Application Icons Third party Application Interface ACA Application Interface Test Method We will provide the subsystem with dummy data of array Lists and verify 1
32. of the team member performing and recording test report e Output Results what the test yield as results e Pass fail Criteria Criteria if the test passed of failed e Comment Any comments relevant to the test as well as a description of any errors System Test Plan Version 1 0 4 Reflection System Test Plan Echo 9 4 Bug Report Each of the bug report will consist of the following section e Bug ID A unique ID for each bug e Test ID The ID corresponding to the test case e Test Date The date the bug was first observed e Priority The priority of the bug to be fixed with respect to severity low medium high critical e Tester Name of team member performing and recording test report e Fixer Name of team member who fixed the bug e Bug Description A short summary about the bug and what caused it e Resolution Date When the bug was fixed e Bug Comments Any comments on the bug or defect System Test Plan Version 1 0 48 Reflection System Test Plan Echo 10 Test Schedule System Test Plan Version 1 0 49 Hardware Testing 11 1 14 11 5 14 Unit Testing 11 5 14 11 15 14 GUI Listener Testing 11 5 14 11 15 14 Event Testing 11 5 14 11 15 14 Request Processor Testing 11 5 14 11 15 14 Voice Input Testing 11 5 14 11 15 14 Command Validator Testing 11 5 14 11 15 14 Command Processor Testing 11 5 14 11 15 14 Power Button Testing 11 5 14 11 15 14 Request Handler Testing 11 5 14 11 15 14 Application Request 11 5 14 11 1
33. pted Test Description Priority ID Results UPF1 Display Application Display data We will provide the High Formatter data to method with a test string display of display data and see 1f it will correctly display data passed Table 3 10 Phone Formatter Unit Test System Test Plan Version 1 0 30 Reflection System Test Plan Echo 3 2 10 Data Formatter Test Model Test Description Priority Priority Input Excepted ID Results Data Parser String request UDF1 We will provide the subsystem with a string and see 1f the request is properly sent to the data storage manager We will provide the subsystem with test strings and see 1f it combines it correctly and sends it to the correct module UDRF3 Data Request Formatter 3 2 11 Data Storage Strings Application Data Table 3 11 Data Formatter Unit Tests Test Model Input Excepted ID Results Test Description UDS1 Data String String from Storage database UDS2 Data Strings Strings into Storage database Data String String from Retrieval database Table 3 12 Data Storage Unit Tests System Test Plan Version 1 0 31 string and see 1f it stores We will send requests to High the data base to retrieve data We will provide the High the information in the right location subsystem with a test We will receive data from High the database from dummy requests Reflection System Test Plan 3 3 Component Test 3 3 1 Input Layer Ech
34. r UDP2 gt Handler Request Input JSON Object lt JSON Object Output JSON Object Test Method We will provide the module with a JSON object and verify if it outputs the other JSON object on ACA of mirror Critical Priority Critical Array List of Apps with package Info We will provide the module with JSON object that has list of apps to pull the information and we will verify 1f the module pulls the package info for the requested Apps Critical UDP3 Request Handler Table Request We will provide this module with Table of favorite Apps and will verify that it shows the Icons to the user Critical UDP4 Command Processor String String We will provide this module with a valid string and verify that 1t sends the string to Application request processor to perform the action System Test Plan Version 1 0 28 Reflection System Test Plan Echo UDPS Command String None We will provide the Medium Processor module with a valid command and verify if it discards the command since it will be invalid for the situation UDP6 Application Android ACA The Module will be Critical Request OS Call interface provided
35. rightness E 10 Power Button Button iai kax E l Table 2 4 Requirements mapping for Presentation Layer System Test Plan Version 1 0 22 Reflection System Test Plan Echo Data Storage Layer Requirement Requirement Name Data Data Request Data Retrieval Data Storage Number Parser Formatter 3 Android Control Application 3 Display Multiple Application Icons Switch between Applications 34 Voice Recognition Y Speakers Mounted on Echo LEE kusa EEE 3 3 3 3 3 8 Resolution and Brightness 3 49 Mimoto Power Button En Table 2 5 Requirements Mapping for Data Storage Layer 1 2 4 How To Application T 9 System Test Plan Version 1 0 23 Reflection System Test Plan Echo 3 Test Items This section details the separate subsystems of the Echo Mirror system and their tests Each table with show their unique test ID the component or module being tested the input that will take the expected output when that input 1s used and how to test that specific module or component The tests will be composed of different tests including unit tests for each module hardware tests for the systems physical components integration tests for system interfaces and system validation tests to ensure the system performs correctly HARDWARE TESTING UNIT TESTING COMPONENT TESTING INTEGRATION TESTING SYSTEM VALIDATION Input Layer i mi System Power Power Input O Edi
36. t E S 38 6 1 Customer Requiem ld o es eee 38 Oia Android Control ApplcalOM tel iia 38 6 1 2 Display Multiple Apply Catton XXX NN AB N de b n Ee ban nda E n n nen A 38 6 1 3 Switch between AppUcatiOnS daa aaa iia 38 OLT Voice RECOSMION yy en a e K Dedi a 38 Bb Hv LOAP CaO NA ken Ken a SS E e sra eee KE k n 38 0 10 Speakers Mounted on Ecler be Key An 39 Od MICRO DOM si sia 39 Glo POWER ans 39 Diz PACK A RS GUI Hel l is cian 39 A So da a oso 39 O22 MITO ODIN 39 E O COO I od LO AT 40 624 Power Cable ansias 40 WR a ce Wee Cit Cie AA AA 40 6 3 1 Voice Command Recognition Latency keke kek 4 64 Naa A 40 OA TVS et VAN gst eased tas sara AA cigs ida 40 OAZ i SN hS SN ND A AA AN 4 64 3 Heat DISSPANON kile ne ribo es park d s kek DNA d r ka we kure Na kk Kel 4 ds Tesine APPO O Wes i al neke ab NEN e e N le Aka Se NN e K 41 TA Dn O a 41 A A a An Y R E RN iie e KA o re 41 Jab COMPONEN LE neyan ee re KO ay ko Ae O Ke e l aNG kaa eee 41 ASO DOST MI On AAA ke on o a e O en ee eee A ee ee 41 Jab System valldation TES a NA NA Lc ljx onxo Y _T_WTT_ r 42 fals Hardware Lestat A 42 System Test Plan Version 1 0 3 Reflection System Test Plan Echo Zade EE MC laa 42 Los OC WG 0 Daan AA AAP AA AA 43 BS Mem Pass EC rJ N 44 A ca lc SP NM AN 44 ER A a e 44 Bl Component kesa aaa lado 46 De ABN A nn NAGA TANAN 41 IL System Test CL AA 47 Dig SA ON 47
37. t the Data Processing Layer can use System Test Plan Version 1 0 16 Reflection System Test Plan 2 2 2 Subsystem Overview Phone Formatter HW1 Input Layer Voice Command Input Touch Input Formatter C2 Data Processing Layer Touch Input Processor Data Processor Echo Power Button Input HW4 Hardware Input Processor Presentation layer Output Manager Echo Formatter Figure 2 2 Architecture Design Diagram System Test Plan Version 1 0 17 DS7 DS1 Data Storage Layer Data Formatter Data Storage Manager Reflection System Test Plan Echo 2 2 3 Requirements Mapping Requirement Requirement Name Input Layer Data Data Presentation Number Processing Storage Layer Android Control Application Display Multiple Ka Switch between an LER TERS NR RR 34 Voice Recognition A 3 5 How To Speakers Mounted on NO Eat EEE O N Bluetooth TEO Resolution and ee Power Button Table 2 1 Architectural Requirements Mapping Table System Test Plan Version 1 0 18 Reflection System Test Plan Echo PNG Detailed Design Specification 2 3 1 Module Overview HW1 Input Layer Voice Command Input Data Processing Layer T3 p t Processor Data Processor bu een o j E3 a Presentation layer Data Storage Layer Ls sik DS3 Ds4 5 Figure 2 3 Detail Design Diagram System Test Plan Version 1 0 19 Refle
38. trategy on testing Echo Echo will be tested for completeness on the requirements stated in the SRS The section will also detail when Echo will be considered complete TA Test Phases 7 1 1 Unit Test As each of the subsystems are being developed the unit tests will be performed on each of the modules of every subsystem by the members developing that particular module 7 1 2 Component Test Component tests will be performed on each of the subsystems and will also be done by the team members that developed that particular subsystem The following list shows the subsystems that will be tested e Touch Input Subsystem e Voice Command Subsystem e Power Input Subsystem e Touch Input Processor Subsystem e Hardware Input Processor Subsystem e Data Processor Subsystem e Data Formatter Subsystem e Data Storage Manager Subsystem e Output Manager Subsystem e Phone Formatter Subsystem e Echo Formatter Subsystem e Server 71 3 Integration Test Integration testing will be done by combining all of the modules into their respective subsystem and then testing those subsystems This test will be done to verify the integrity of all inter subsystem and interlayer interfaces and interactions Each layer will be tested to ensure that they perform their function as stated in the Detailed Design Specification System Test Plan Version 1 0 4 Reflection System Test Plan Echo 7 1 4 System Validation Test The final test that will be done on the s
39. ware The user may change any of the hardware used 3 Moderate Support amp in Echo All the specifics of the hardware used in Maintenance the system will be included in the user manual The instructions on replacing the hardware will be included in the troubleshooting guide Source Code amp Any code written or used by the development 3 Moderate Documentation team and any documentation for the system will be readily available for everyone to see post production Table 2 5 Maintenance and Support Requirements 13 Reflection System Test Plan Echo 2 1 6 Other Requirements Requirement Description Priority 8 1 Security and When communicating via Bluetooth the 4 Low Privacy Android M application should ensure the security and privacy of the user information 8 2 Bluetooth Range The phone needs to be within the Bluetooth 2 High range of Echo There should be a clear line of sight between Echo and the phone for the most stable connection 8 3 Android The Application shall be designed to run on all 1 Critical Version Support Android versions between 4 0 3 and 4 4 8 4 Moisture Control Echo will prevent moisture from damaging 2 High components within the system Table 2 6 Other Requirements System Test Plan Version 1 0 14 Reflection System Test Plan Echo 2 2 Architectural Design Specification This subsection highlights the architecture outlined in the ADS
40. y of voice commands both those known to the system and those that the system will not recognize I3 Input Layer User interaction Power to the The external power button Critical with external screen and will be tested by confirming power button Android TV power to the screen and box Android TV box is turned on and off by pressing the button 14 Data Parsed Voice Application We will provide the Layer Critical Processing command Interface with parsed voice command Layer and verify 1f the I5 Data JSON Object Application We will provide the layer with High Processing Icons JSON object and verify if it Layer displays the Application Icons of the selected apps on the _ Screen I6 Data ArrayLists None We will send data to the Critical Storage layer and see if it properly Layer stores it into the database I7 Data Request Application We will verify this by Critical Storage Information requesting data from the Layer database and see if the layer packages it correctly and sends it to the proper location I8 Presentation Application Application We will provide the method High Layer Interface with a test string of display data and see 1f it will correctly display data passed Table 3 17 Integration Tests System Test Plan Version 1 0 35 Reflection System Test Plan 4 Risk 4 1 Risk Overview Echo This section will go through the risks that we might encounter as we test the Echo The table below will show specific risks
41. ystem will be the validation tests It will ensure that all of the requirements by the customer and the development team mentioned in the SRS are met It will validate that the functionality of the Echo is exactly as stated in the requirements 71 5 Hardware Test As the applications needed for the Echo are being developed the hardware that goes along side 1t will also be assembled and tested Each hardware piece will be tested individually and then they will be tested again after integrating them with other hardware pieces and the software apps Taki Test Metrics Priority Description Pass Criteria Fail Criteria Critical These features must 100 Tess than 100 be completed for they are critical to the functionality of the system The system would not be able to function without them High These are the non 9090 Less than 9090 critical features of the system The system will have some functionality without them but they should be completed for greater user experience Moderate These would have 15904 Less than 75 moderate impact on the user experience __ Low These features do not O N A impact the performance of the system and are considered to be for future plans System Test Plan Version 1 0 42 Reflection System Test Plan PoP Test Tools Team Reflection will be using the following tools for testing e Excel e JUnit e GitHub System Test Plan Version 1 0 43 Echo Reflection
Download Pdf Manuals
Related Search