Test Plan and Cases (TPC)

Transcription

1 Test Plan and Cases (TPC) GOTRLA Team 15 Deepak Earayil Project Manager & Software/System Architect Ankith Nagarle Prototyper & Operational Concept Engineer Aayush Jain Feasibility Analyst & Project Manager Presha Thakkar Lifecycle Planner and Requirements Engineer Suhani Vyas Requirements Engineer & Feasibility Analyst Anushila Dey Software/System Architect & Lifecycle Planner Nidhi Baheti Operational Concept Engineer & Prototyper Elaine Lo Shaper & Quality Analyst October 19, 2014

2 Version History Date Author Version Changes made Rationale 10/18/14 Elaine Lo 1.0 Completed sections 1 & 2 Initial draft for the DC package ii

3 Table of Contents TEST PLAN AND CASES (TPC)... I VERSION HISTORY... I TABLE OF CONTENTS... III TABLE OF TABLES... IV TABLE OF FIGURES... V 1. Introduction Test Strategy and Preparation Hardware preparation Software preparation Other pre-test preparations Requirements Test Identification Test Identifier... Error! Bookmark not defined. 3.2 Test Identifier... Error! Bookmark not defined. 4. Resources and schedule Resources Staffing and Training Needs Schedule iii

4 Table of Tables Table 1: Requirements Matrix... 7 Table 2: TC Check report completeness... 8 Table 3: TC Check report correctness... 9 Table 4: Testing Schedule TPC_DCP_F14a_T15_V1.0 iv Version Date: 06/22/12

5 Table of Figures Figure 1: <Figure Title>... Error! Bookmark not defined. TPC_DCP_F14a_T15_V1.0 v Version Date: 06/22/12

6 1. Introduction The purpose of the TPC is to provide a plan for testing the GOTRLA application developed by our team. This document will outline the test cases needed in order to show that our application can meet all the capability requirements, project requirements, and levels of service as well as some non-conventional cases. The scope of testing will include sunny day cases as well as rainy day cases of both the mobile application and the web interface. The type of testing we are going to implement is black-box testing where we will give specific inputs and test to see if the results are as expected. 6

7 2. Test Strategy and Preparation The following test strategies will be used to ensure the successful system operation Agile continuous integration: Different parts of the software will be developed at the same time so we will continuously test to see that they can integrate with each other Boundary and exit/entry criteria between unit testing and integration testing: Pass functionality test cases listed in this report to determine that each feature performs as expected and that the features are able to integrate with each other Test environment preparation: Pass user acceptance testing performed by clients and volunteer testers Requirements-test traceability: matrix will be used to ensure that the capabilities requirements, project requirements, and level of services will be evaluated by the test cases 2.1 Hardware preparation The following hardware are needed in order to test our system PC: used to test our system in Windows OS MacBook: used to test our system in OS X iphone: used to test our application on an apple phone Android phone: used to test our system on an android phone 2.2 Software preparation The following software are needed in order to test our system IE/Chrome/Firefox/Safari: the web interface needs to be tested on multiple browsers to see system compatibility across the different platforms GOTRLA application: our application needs to be downloaded onto the phone via either Google Play store or Apple app store 2.3 Other pre-test preparations There are no other pre-test preparations required. 2.4 Requirements Table 1: Requirements Matrix Requirement ID Verification Type Test Case ID (if applicable) CR-1 Admin can edit staff data Testing TC-02 CR-2 Staff can edit class, girls, and Testing TC-02 volunteer data CR-3 Coaches can access rosters Testing TC-03, TC-04, TC-06, TC-07, TC-08 CR-4 Reset/Update password Testing TC-01 PR-1 Accessible through desktop and mobile devices Testing TC-01, TC-10 7

8 PR-2 Budget requirements LOS-1 Reliability LOS-2 Usability LOS-3 Maintainability Analysis Analysis Demonstration Inspection 3. Test Identification 3.1 TC-01 User permissions Test Level Software item level Test Class Erroneous tests Test Completion Criteria The test for user permissions will be completed when - The system allows admin and staff to access both the web interface and the mobile application - The system allows the coaches to access the mobile application and see only his/her class roster information Test Cases Table 2: TC Check admin access to web interface TC Check admin access to web interface This item will check to see that the admin is able to login to the web interface M User must already have been added into the database as admin and given permission to access the web interface Login information is temporarily stored Admin enters username and password Admin is able to login to the website and navigated to main screen page Pass criteria: user is navigated to main screen page Fail criteria: message appears saying that the login information is invalid CR-4 & PR-1 8

9 Table 3: TC Check admin access to mobile application TC Check admin access to mobile application This item will check to see that the admin is able to login to the mobile application M User must already have been added into the database as admin and given permission to access the mobile application Login information is temporarily stored Admin enters username and password Admin is able to login to the website and navigated to main screen page Pass criteria: user is navigated to main screen page Fail criteria: message appears saying that the login information is invalid CR-4 & PR TC-02 Admin/staff usability Test Level Software item level Test Class Erroneous tests Test Completion Criteria The test for admin/staff usability will be completed when - Admin and staff are allowed to change data regarding coaches, classes, and students - Admin is allowed to change data regarding staff Test Cases Table 4: TC Admin and staff change data on coaches, classes, and students TC Admin and staff change data on coaches, classes, and students Admin and staff are given the ability to update, delete, or add information regarding coaches, and students M Admin and staff have access to the web interface and have been given permissions to alter the data The new/altered data is saved into the database or deleted data is removed from the database 9

10 Adding/editing data from both admin and staff - Classes: Roster, volunteer(s), duration - Students: First name, last name, age, payment made, waiver signed, phone no, medications Special problems, roster The new/altered data is saved into the database in the way that it was entered into the system. The deleted data is removed from the database Pass criteria1: database is updated according to the inputs the user entered Pass criteria2: data is removed according to whether the user removed them TC-01 CR-1 & CR TC-03 Coach usability Test Level Software item level Test Class Erroneous tests Test Completion Criteria The test for user permissions will be completed when - Coaches are able to save attendance of their class - Coaches are able to view/edit certain data of their students (i.e. payment made or waiver signed) Test Cases Table 5: TC Coaches save attendance TC Coaches save attendance Coaches are given the ability to save the attendance of fellow coaches and students M Coaches have access to the mobile application and have been given permissions to save attendance The attendance data is saved into the database Check yes if a student/coach is present at a session or leave blank if they are not The attendance data is saved into the database in the way that it was entered into the system Pass criteria: database is updated according to the inputs the user entered them 10

11 TC-01 & TC-02 CR-3 Table 6: TC Coaches alter student data TC Coaches alter student data Coaches are given the ability to change certain data of students S Coaches have access to the mobile application and have been given permissions to alter data The altered student data is saved into the database Yes or no if student made a payment Yes or no if student had their waver signed The altered student data is saved into the database in the way that it was entered into the system Pass criteria: database is updated according to the inputs the user entered them TC-01 & TC-02 CR TC-04 Generate report summary Test Level Software item level Test Class Erroneous tests Test Completion Criteria The test for generate report summary will be completed when - The system generates a complete and correct summary report - The generated summary report is correctly displayed on the monitor Test Cases Table 7: TC Check report completeness TC Check report completeness Reports generated contains the attendance for all the classes M 11

12 Attendance data is saved in the database Enter roster, week, and save format Reports that contain the attendance data for each class Pass criteria: report for each roster is able to be generated TC-01, TC-02, & TC-03 CR-3 Table 8: TC Check report correctness TC Check report correctness Report generated contains the attendance for the students in the class and show accurate data on what the coaches logged in for the attendance M Attendance data is correctly saved in the database Enter roster, week, and save format Reports that contain the attendance data for each class Pass criteria: report for each roster shows accurate information on what was sent by the coaches TC-01, TC-02, & TC-03 CR-3 12

13 4. Resources and schedule <<In this section, specify the people, time, budget, resources and schedule allocated for testing, etc. >> 4.1 Resources << Identify all resources need for testing, such as test data set, software, budget, and etc >> 4.2 Staffing and Training Needs << Identify the stakeholders responsible for managing, designing, preparing, executing, witnessing, inspecting and resolving test items. In addition, provide the groups responsible for providing items to be tested. Specify test-staffing needs by skill level. Identify training options for providing necessary skills. >> 4.3 Schedule Table 1: Testing Schedule Date Test Identifier Responsible person Resources Training needs 01/02/09 TC to TC John Smith Report test data sets, N/A JUnit 13