Test Plan and Cases (TPC)

Transcription

1 Test Plan and Cases (TPC) MedFRS Device Diagnostic Software Team 16 Misha Dowd Delnaz Gundevia Anfal Abdul Jaleel Nanda Kishore Kolleje Rao Anupam Kumar Jackie Cheng Project Manager Life Cycle Planner System Architect System Requirements Engineer Feasibility Analyst IIV & V i

2 Version History Date Author Version Changes made Rationale 10/23/13 AAJ,N K,DG, MD 10/23/13 AAJ,N K,DG, MD,AK,JC 1.0 Original template from 577a; Changed all sections Add Content for DC package 1.1 Changed section 3 Add Content for DC package 12/02/13 AAJ 2.0 Added test cases and deleted obsolete For TRR Package ones 12/02/13 AAJ 2.1 Added information For TRR ARB 12/09/13 DG,AA J 2.2 Added information and formatted For TRR ii

3 Table of Contents TEST PLAN AND CASES (TPC)... I MedFRS Device Diagnostic Software... i VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... V 1. Introduction Purpose of the TPC Document Status of the TPC Document Test Strategy and Preparation Hardware preparation Software preparation Requirements Test Identification Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier iii

4 3.8 Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Test Identifier Resources and schedule Resources Staffing and Training Needs Schedule iv

5 Table of Tables Table 1: Requirements Matrix... 8 Table 2 : TC Authorize Application... 9 Table 3 : TC Failed Authorize Application Table 4 : TC Collect correct Victim Data Table 5 : TC Collect incomplete Victim Data Table 6 : TC-03 Barcode Scanning Table 7 : TC-04 Application Data Sync Table 8 : TC-05 Application Performance Table 9 : TC-06 Database Performance Table 10 : TC-07 Data Security Table 11 : TC Add disaster Table 12 : TC Add empty disaster Table 13 : TC Choose disaster Table 14 : TC EMT Assignment Table 15 : TC Add empty EMT Assignment Table 16 : TC Search victim Table 17 : TC Search victim Table 18 : TC Update table Table 19 : TC Deletion from table Table 20 : TC Erroneous Update Table 21 : TC Manage Buildings/hubs/disasters in database v

6 Table 22 : TC Manage Buildings/hubs/disasters in database Table 23 : TC Add building Table 24 : TC Erroneous Entry Table 25 : TC Login Successful Table 26 : TC Denied Access Table 27 : TC Add User Table 28 : TC Add empty user Table 29 : TC Add volunteer Table 30 : TC Add empty volunteer Table 31 : TC Manage User Table 32 : TC Invalid User Update Table 33 : TC Resend OTP Table 34 : TC Invalid volunteer update Table 35 : TC Record Victim Transportation Table 36 : TC Record Incomplete Victim Transportation Table 37 : TC Update Victim Transportation Table 38 : TC Update Erroneous Victim Transportation Table 39 : TC-22 Log out Table 40: Testing Schedule vi

7 1. Introduction 1.1 Purpose of the TPC Document This document aims to state how to test the Medical First Response System Device Diagnostic Software project. This is achieved by identifying potential situations that the project may run into and then creating test cases about them. This will give the development team and stakeholders a clearer picture of the application s functions and features; thus, aiding the development team in creating a better application. 1.2 Status of the TPC Document The status of the TPC is currently at the Transition Readiness Review phase (version 2.2). This version has the set of test cases created for the functionalities of the project that were implemented within the timeframe and is the final version created by the team. 7

8 2. Test Strategy and Preparation Agile Continuous Integration: the mobile application will be built in phases and tested on the simulator first, and then it will be distributed for Beta Testing 2.1 Hardware preparation ios Device to test the application Distribution Certificates to distribute Ad-Hoc application to testers. 2.2 Software preparation The software to be used: iphone Simulator to test the Application Xcode Instruments Debugger to test the Application Performance and Memory Testing To distribute app for beta testing: 1. Optionally, create an itunes Connect app record. 2. Register all test devices. 3. Create a distribution certificate. 4. Create an ad hoc provisioning profile. 5. Update the build string in build setting. 6. Archive and validate app. 7. Create an ios App Store Package. 8. Install the app on test devices. 9. Solicit crash reports from testers. 2.3 Requirements Table 1: Requirements Matrix Requirement ID Verification Test Case ID (if applicable) Type WC_2741 Testing TC-01, TC-15, TC-16, TC- 17, TC-18, TC-19,TC-22 WC_2634 Testing TC-02 WC_2635 Testing TC-02 8

9 WC_2636 Testing TC-02 WC_2637 Testing TC-02 WC_2638 Testing TC-02 WC_2755 Testing TC-02 WC_2757 Testing TC-02 WC_2641 Testing TC-03 WC_2639 Testing TC-03 WC_2797 Testing TC-04. TC-11 WC_2796 Testing TC-05, TC-06, TC-08, TC- 09, TC-12, TC-13, TC-14 WC_2742 Testing TC-06, TC-20,TC-21 WC_2760 Testing TC-06, TC-10 WC_2762 Testing TC-06 WC_2640 Testing TC-10 WC_2756 Inference 3. Test Identification 3.1 Test Identifier TC-01 Application Authentication Test Level Software Item level Test Class Functionality test, Erroneous Test Test Completion Criteria -If user enters the correct OTP then he is authorized else not authorized Test Cases Table 2 : TC Authorize Application TC Application Authorization 9

10 The Volunteer must be a registered User Access is allowed for the volunteer into the app Inputs Include the One Time Pass Key Acknowledge message from the server on successful authorization. Pass: If the server returns Acknowledge (ACK) Fail: If the server times out or returns Error (ERR) TC WC_2741 Table 3 : TC Failed Authorize Application TC Failed Application Authorization Database is initiaized Access is restricted for the volunteer into the app Inputs Include the One Time Pass Key Error message Pass: If server does not allow him access WC_ Test Identifier TC-02 Collect Victim Data Test Level Software Item level 10

11 3.2.2 Test Class Functionality Test, Erroneous Test Test Completion Criteria -All the data entered by the volunteer must be stored in the Dictionary Object of the Application -Victim records without all required fields should not be added to the database Test Cases Table 4 : TC Collect correct Victim Data TC Collect correct Victim Data Mobile application and its data Entry Fields The Application must be authorized The data is sent to the Server Inputs rely on specific fields, like Age is a number, location is a string and so on A dictionary object with all the victims data Pass: If all the attributes have data or are blank entry Fail: If a field in an object has invalid character WC_2634, WC_2635, WC_2636, WC_2637, WC_2638, WC_2755, WC_2757 Table 5 : TC Collect incomplete Victim Data TC Collect Victim Data Mobile application and its data Entry Fields 11

12 The Application must be authorized The data is sent to the Server Volunteer inputs victim data with some required fields empty Volunteer is asked to fill in the required fields Pass: If the incomplete record is added to the database WC_2634, WC_2635, WC_2636, WC_2637, WC_2638, WC_2755, WC_ Test Identifier TC-03 Bar Code Scanning Test Level Software Item level Test Class Functionality Test Test Completion Criteria Bar Code must retrieve a valid bar code number Test Cases Table 6 : TC-03 Barcode Scanning TC-03 Bar Code Scanning Mobile application Bar Code Scanning Want to have Victim Data has been collected 12

13 Victim information is sent along with the barcode Tag containing the Barcode Number The Barcode number Pass: If the barcode is successfully recognized Fail: if the system fails to recognize the barcode Barcode format is known TC WC_2639, WC_ Test Identifier TC-04 Application Data Sync Test Level Software Item level/ System Performance Test Class Functionality Test Test Completion Criteria A valid object must be sent to the server on submitting the form Test Cases Table 7 : TC-04 Application Data Sync TC-04 Application Data Sync Mobile application Data sync to the server Victim Data Entry by Volunteer Successful Data Sync with Server On Click of submit button by the volunteer Successful Acknowledge message by the server 13

14 Pass: If data sync is successful Fail: If data is not received by the server Data format is known TC-02-01, TC-03 WC_ Test Identifier TC-05 Application Performance Test Level System Performance (level of service) Test Class Timing Test Test Completion Criteria Application should be received formatted and send data offering the best performance possible Test Cases Table 8 : TC-05 Application Performance TC-05 Application Performance Data Entry and Data Sync Want to have Volunteer can move on to the next Victim Data Entry and Server Acknowledgment Valid inputs for the specified fields Accepted level of performance Pass: If the average time is less than the accepted level Fail: If more time is taken for the process than the accepted level 14

15 TC-02-01, TC-03 WC_2796, WC_2634, WC_2635, WC_2636, WC_2637, WC_2755, WC_ Test Identifier TC-06 Database Performance Test Level System Performance (level of service) Test Class Timing Test/ Erroneous Test Test Completion Criteria Data should be written and read without any loss or corruption Test Cases Table 9 : TC-06 Database Performance TC-06 Database Performance Read and write data from database Want to have Data should be successfully received and validated by the server Acknowledgement after successful transaction Data/Request from the client Transaction success Pass: Read/write/Update delete is successful Fail: If it fails more than the desired level Database is online and running TC-07 WC_2796, WC_2742, WC_2760, WC_

16 3.7 Test Identifier TC-07 Data Security Test Level System Performance (level of service) Test Class Erroneous Test Test Completion Criteria Data encrypted and decrypted without any loss Test Cases Table 10 : TC-07 Data Security TC-07 Data Security Encrypt and Decrypt data Want to have Data should be successfully received and validated by the server Post processing of data to store or send it back to the client Data received from the client Successful decryption or Encryption of data Pass: Data is encrypted or decrypted with minimal loss Fail: If loss is more than the desired level Encryption and Decryption certificates are valid WC_

17 3.8 Test Identifier TC-08 Disaster Entry Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria -Supervisor must add disaster record into the database - Supervisor must not add disaster record with an empty name and/or start date into the database Test Cases Table 11 : TC Add disaster TC Add disaster The supervisor must be logged in and chose emergency The disaster is added to the database User inputs disaster details and clicks Add System inserts a new disaster record into the database and redirects to supervisor disaster homepage Fail: If record is not added to the database and/or supervisor does not reach disaster homepage WC_

18 Table 12 : TC Add empty disaster TC Add empty disaster The supervisor must be logged in and chose emergency The disaster is not added to the database User inputs disaster details with some empty required fields and clicks Add System displays error message and redirects to submitted disaster form Fail: If record is added to the database WC_ Test Identifier TC-09 Disaster Choice Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria Supervisor must see a list of only open disasters and then goes to the homepage of the disaster chosen Test Cases Table 13 : TC Choose disaster TC Choose disaster 18

19 The supervisor must be logged in and chose emergency The supervisor accesses all data related to the chosen disaster User chooses disaster System redirects to supervisor disaster homepage Fail: If supervisor does not reach disaster homepage TC WC_ Test Identifier TC-10 Add EMT Assignment Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria -Supervisor must add EMT assignment into the database - Supervisor must not add EMT assignment with an team number and/or building into the database Test Cases Table 14 : TC EMT Assignment TC Add EMT Assignment The supervisor must be logged in and chose emergency 19

20 The EMT Assignment is added to the database User inputs EMT team number and building details and clicks Add System inserts a new EMT Assignment record into the database and redirects to supervisor disaster homepage Fail: If record is not added to the database and/or supervisor does not reach disaster homepage WC_2760,WC_2640 Table 15 : TC Add empty EMT Assignment TC Add empty EMT Assignment The supervisor must be logged in and chose emergency The EMT Assignment is not added to the database User inputs EMT Assignment details with some empty required fields and clicks Add System displays error message and redirects to submitted EMT Assignment form Fail: If record is added to the database WC_2760,WC_ Test Identifier TC-11 Search for victims Test Level Software Item level 20

21 Test Class Functionality Test, Erroneous Test Test Completion Criteria -Supervisor must get a subset of Victim records with their latest information from the database which matches his search criteria Supervisor must not get Victim records from the database which do not match his search criteria Test Cases Table 16 : TC Search victim TC Search victim The supervisor must be logged in and chose emergency The supervisor gets a list of matching victims User inputs victim details and clicks Search System returns a subset of victim records from the database and redirects to supervisor disaster homepage Fail: If matching record is not shown to the supervisor TC-03 WC_2797 Table 17 : TC Search victim TC Eliminate victim record The supervisor must be logged in and chose emergency The supervisor not get mismatched victims User inputs victim details and clicks Search System returns a subset of matching victim records from the database and no mismatching 21

22 ones and redirects to supervisor disaster homepage Fail: If mismatching record is shown to the supervisor WC_ Test Identifier TC-12 Manage Emergency tables Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria -Supervisor must update and delete information in the database which only matches his criteria -Supervisor must not update records with empty required fields in the database Test Cases Table 18 : TC Update table TC Update table The supervisor must be logged in and chose emergency The supervisor updates information in the table User selects record to be updated, enters the updated information, and clicks update 22

23 System updates the information of only the specified record in the table and shows the updated information to the supervisor Fail: If specified record is not updated or an unspecified record is updated TC-10-01,TC WC_2796 Table 19 : TC Deletion from table TC Deletion from table The supervisor must be logged in and chose emergency The supervisor deletes information from the table User selects record to be deleted and clicks delete System deletes only the specified record from the table and shows the updated table to the supervisor Fail: If specified record is not deleted or unspecified record is deleted TC-10-01,TC WC_2796 Table 20 : TC Erroneous Update TC Erroneous Update The supervisor must be logged in and chose emergency The specified record is not updated in the system User selects record to be updated, enters the updated information and clearing some required fields of the record, and clicks update 23

24 System does not update the any record from the table and displays error and shows the submitted update form to the supervisor Fail: If specified record is updated TC WC_ Test Identifier TC-13 Manage Buildings/hubs/disasters in the database Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria Supervisor enters the buildings/hub/disasters and the database gets updated with the latest records Test Cases Table 21 : TC Manage Buildings/hubs/disasters in database TC Update buildings/hub/disasters in database Database is initialized and buildings are added to it, the supervisor has logged in and clicked non-emergency Information in database has been updated Supervisor enters the building data and clicks submit The building/hub /disaster data is updated into the database. 24

25 Fail: : If record is not updated in the database and/or supervisor does not reach disaster homepage TC WC_2796 Table 22 : TC Manage Buildings/hubs/disasters in database TC Delete Buildings/hub/disasters data Database is initialized and buildings are added to it, the supervisor has logged in and clicked non-emergency Information in database has been deleted Supervisor deletes the building data and clicks delete The building/hub /disaster data is deleted from the database. Fail: If record is not deleted in the database and/or supervisor does not reach disaster homepage WC_ Test Identifier TC-14 Add buildings to the database Test Level Software Item level Test Class Functionality Test, Erroneous Test 25

26 Test Completion Criteria -Supervisor must add the building information to the database -Supervisor must enter all required fields to the building form Test Cases Table 23 : TC Add building TC Add building Database has been initialized and the building/hub/disaster is not in the database. Supervisor has logged in and clicked nonemergency Building is added to the database. Supervisor click Add Building/Hub button; he enters all required fields; he clicks Submit Form button. System validates input; insert the new record into the database; Redirect the webpage to View Building s page Fail: If an require field is not fill out None WC_2796 Table 24 : TC Erroneous Entry TC Erroneous Entry Database has been initialized and the building/hub/disaster is not in the database. Supervisor has logged in and clicked nonemergency Building is added to the database. Supervisor click Add Building/Hub button; he left some required field empty; he clicks Submit Form button. 26

27 System does not insert the record into the database; it displays error and shows the submitted Add Building form to the supervisor Fail: If a record is created and inserted into the database None WC_ Test Identifier TC-15 Login to MedFRS Website Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria -Website user successfully login with proper user name and password -Website user being denied access without proper user name or password Test Cases Table 25 : TC Login Successful TC Login Successful The system and databases have been initialized and populated Supervisor and Transport Coordinator has logged into the system while all others see an error message and are redirect to the login page 27

28 User enters his username and password in the Login page; User clicks "Log In" button Redirect to MedFRS Supervisor/Transport Coordinator Homepage Fail: If user is being denied access Supervisor and Transport Coordinator has logged into the system TC WC_2741 Table 26 : TC Denied Access 1 TC Denied Access1 The system and databases have been initialized and populated User is not allowed access to the system User enters his username and password in the Login page; User clicks "Log In" button Display error message and redirect to MedFRS Login Page Fail: If user is able to access the system None WC_2741 None WC_ Test Identifier TC-16 Add Individuals to list of allowed users Test Level Software Item level 28

29 Test Class Functionality Test, Erroneous Test Test Completion Criteria -Supervisor must add system user s record into the database - Supervisor must not add user record with empty credentials (name, , USCID) into the database Test Cases Table 27 : TC Add User TC Add user The supervisor must be logged in The user is added to the database User inputs user details (name, , date of birth, id) and clicks Add System inserts a new user record into the database and redirects to supervisor nonemergency homepage Pass: Confirmation messages is displayed and Supervisor reaches the non-emergency homepage Fail: If failure message is displayed and Supervisor is taken back to add user page 1. Password is entered by supervisor 2. Information is provided physically by the user WC_2741 Table 28 : TC Add empty user TC Add empty user credentials The supervisor must be logged in The user is not added to the database User inputs user details with some invalid required fields and clicks Add 29

30 System displays error message and redirects to submitted user registration form Fail: If record is added to the database 1. Password is entered by supervisor 2. Information is provided physically by the user WC_ Test Identifier TC-17 Add Volunteers to list of allowed users Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria -Supervisor must add volunteer s record into the database - Supervisor must not add volunteers with empty credentials (name, phone number, , USCID) into the database Test Cases Table 29 : TC Add volunteer TC Add volunteer The supervisor must be logged in The volunteer is added to the database User inputs user details (name, , date of birth, phone, id) and clicks Add System inserts a new volunteer record into the database and redirects to supervisor nonemergency homepage 30

31 Pass:Confirmation messages is displayed and Supervisor reaches the non-emergency homepage Fail: If failure message is displayed and Supervisor is taken back to add user page 1. System generates one time password and sends with the registration link 2. Volunteer has to use the link and register inorder to use the system WC_2741 Table 30 : TC Add empty volunteer TC Add empty volunteer credentials The supervisor must be logged in The user is not added to the database Supervisor inputs volunteer details with some invalid required fields and clicks Add System displays error message and redirects to submitted disaster form Fail: If record is added to the database 1. System generates one time password and sends with the registration link 2. Volunteer has to use the link and register inorder to use the system WC_ Test Identifier TC-18 Manage system users Test Level Software Item level Test Class Functionality Test, Erroneous Test 31

32 Test Completion Criteria -Supervisor must update/delete user information in the database - Supervisor must not update user information with empty credentials (name, phone number, , USCID) into the database Test Cases Table 31 : TC Manage User TC Update/delete user The supervisor must be logged in The user information is updated/deleted in the database Supervisor selects a user from a list of users System updates/deletes existing user record into the database and redirects to user management screen Pass: Confirmation messages is displayed and Supervisor reaches the user management screen Fail: If failure message is displayed and Supervisor is taken back to user list page Information is provided physically by the user TC-17-01,TC WC_2741 Table 32 : TC Invalid User Update TC Update/delete user The supervisor must be logged in The user information is not updated with valid inputs Supervisor inputs user details with some invalid required fields and clicks update (such as empty, duplicate id) System displays error message and redirects to submitted user update form Fail: If record is added to the database 32

33 Information is provided physically by the user WC_ Test Identifier TC-19 Resend one-time password to volunteer Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria -Supervisor must resend volunteer one time password link to volunteer - Database must update the access-code for the corresponding volunteer, when the volunteer accesses the link and enters the passcode Test Cases Table 33 : TC Resend OTP TC Resending one time password The supervisor must be logged in The volunteer access-code is updated/deleted in the database Supervisor selects a volunteer from a list of volunteers System generates a passcode and an accesscode for existing volunteer record into the database Supervisor gets a confirmation message from system about the being sent and super is showed user management system 33

34 Pass:Confirmation messages is displayed and Supervisor reaches the user management screen Fail: If failure message is displayed and Supervisor is taken back to user list page 1. Volunteer must information supervisor and request supervisor to generate OTP 2. Volunteer may have lost his device 3. Previous OTP might have expired TC WC_2741 Table 34 : TC Invalid volunteer update TC Resending one time password The supervisor must be logged in The user information is not updated with valid inputs Supervisor inputs user details with some invalid required fields and clicks update (such as empty, duplicate id) System generates a passcode and an accesscode for existing volunteer record into the database Supervisor gets a confirmation message from system about the being sent and super is showed user management system Fail: If the volunteer is no longer an active volunteer 1. Volunteer must information supervisor and request supervisor to generate OTP 2. Volunteer may have lost his device 3. Previous OTP might have expired WC_

35 3.20 Test Identifier TC-20 Record Victim Transportation Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria - Transport Coordinator enters the Victim s barcode, ambulance number and destination hospital - Inserts record into the database and redirects to Homepage Test Cases Table 35 : TC Record Victim Transportation TC Record Victim Transportation Record victim data Tagged Victim has been brought to the hub by the EMT and is to be taken to a hospital by an ambulance and Transport Coordinator is logged onto the website Victim destination and transport is entered into the database and the associated EMT team is unassigned from their building if no validations fail Transport Coordinator enters the Victim's barcode, Ambulance number and destination hospital and clicks "Enter" button Inserts record into the database, redirects to the Transport coordinator's Homepage 35

36 Pass: If barcode, ambulance number and destination hospital are non-empty in the record. Fail: If the fields are empty Transport Coordinator is logged in TC-02-01, TC-04 WC_2742 Table 36 : TC Record Incomplete Victim Transportation TC Record Incomplete Victim Transportation Record victim data Tagged Victim has been brought to the hub by the EMT and is to be taken to a hospital by an ambulance and Transport Coordinator is logged onto the website Victim destination and transport is not entered into the database and Coordinator is asked to resubmit Transport Coordinator enters the Victim's barcode, Ambulance number and destination hospital and clicks "Enter" button Displays error and Redirects to the submitted page Pass: If record is not inserted into database Transport Coordinator is logged in TC-02-01, TC-04 WC_

37 3.21 Test Identifier TC-21 Update Victim Transportation Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria - Transport Coordinator enters the Victim s barcode, ambulance number and destination hospital - Updates the database and redirects to Homepage Test Cases Table 37 : TC Update Victim Transportation TC Update Victim Transportation Update victim data Should Have Transport Coordinator has entered victim tracking in the database, and wants to change an entry Information has been updated in the database if no validations fail. Transport Coordinator clicks "Update" button next to the entry, enters updated data, and clicks "Submit Form" button Redirects to the Update Victim Tracking Form Page, system validates input (all fields are filled out), updates victim tracking record in the 37

38 database, redirects to the Transport Coordinator page Fail: If specified record is not updated or an unspecified record is updated TC WC_2742 Table 38 : TC Update Erroneous Victim Transportation TC Update Erroneous Victim Transportation Update victim data Transport Coordinator has entered victim tracking in the database, and wants to change an entry Information has not been updated in the database as validations fail. Transport Coordinator clicks "Update" button next to the entry, enters updated data, and clicks "Submit Form" button Displays error and Redirects to the Update Victim Tracking Form Page Fail: If specified record is updated TC WC_

39 3.22 Test Identifier TC-22 Log out Test Level Software Item level Test Class Functionality Test, Erroneous Test Test Completion Criteria - User logs out of the system Test Cases Table 39 : TC-22 Log out TC Log out from Website Log out User is logged into the system User is logged out of the system Website user clicks "Log out" button System logs user out and redirects him to MedFRS homepage Pass: If user is logged out User is logged in TC WC_

40 4. Resources and schedule 4.1 Resources Test Data: Mock Victim Sample Data, Supervisor Sample Data and Transport Coordinator Sample Data Software: Xcode Instruments to check performance, iphone Simulator to emulate application, Distribution Certificate to distribute apps Beta Testing: Ad-Hoc Distribution network to test performance on multiple levels 4.2 Staffing and Training Needs Development team is responsible for the entire testing process. The prototyper and developer is responsible for providing the items to be tested. Test staff need to know iphone testing and web app testing. 4.3 Schedule Table 40: Testing Schedule Date Test Identifier Responsible person 10/30/ Nanda Kishore Kollaje Rao 11/18/13 CCD All data adding TCs 12/04/13 All core Capabilities except data security (All Nanda Kishore Kollaje Rao, Anfal Abdul Jaleel Nanda Kishore Kollaje Rao, 40 Resources Xcode Instruments, IPhone Simulator, Apache Server. Chrome, MySQL, Ruby on Rails Command Prompt Chrome, MySQL, Ruby on Rails Training needs N/A N/A N?A

41 excluding TC- 07,TC-19,TC- 21) Anfal Abdul Jaleel Command Prompt, PHP 41