Test Plan and Cases (TPC)

Transcription

1 Test Plan and Cases (TPC) Perfecto Coffee Xpress Consistent Perfection Team 5 Team embers & Roles Chloe Good Yekaterina Glazko Edwards Hays Yucheng Hsieh Atreya Lahiri Jaimin Patel Yun Shen Andrew Tran Name Primary/Secondary Role IIV & V / Quality Focal Point IIV & V Requirements Engineer Software Architect Feasibility Analyst Project anager / Life Cycle Planner Prototyper Operational Concept Engineer 11/02/2018

2 Version History Date Author Version Changes made Rationale 11/02/18 CG 1.1 Some general cleanup, update some WCs to match SSAD inor cleanup 10/22/18 CG, KG 1.0 Initial draft of TPC Initial draft of TPC ii

3 Table of Contents TEST PLAN AND CASES (TPC)... I VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... IV 1. Introduction Test Strategy and Preparation Test Identification Resources and schedule iii

4 Table of Tables Table 1: Requirements atrix... 3 Table 2: TC Validate user input... 6 Table 3: TC Create user account... 7 Table 4: TC Verify user account creation in DB... 8 Table 5: TC Verify Facebook login integration... 9 Table 6: TC Verify user login input Table 7: TC Verify user login in DB Table 8: TC Verify user logout in DB Table 9: TC View recipes - Order page Table 10: TC View recipes Recipes page Table 11: TC Recipe saved - Verify displayed recipes against DB Table 12: TC Recipe deleted - Verify displayed recipes against DB Table 13: TC Recipe selected (Order page) - Verify available recipe actions Table 14: TC Recipe selected (Recipes page) - Verify available recipe actions Table 15: TC Save recipe Table 16: TC Delete recipe Table 17: TC Verify ingredient levels can be modified from base recipe Table 18: TC Verify customized recipes can be modified Table 19: TC Verify Recipe Review modifications and actual recipe modifications match Table 20: TC Verify DB updates Table 21: TC Verify recipe sharing function (share to Facebook account) Table 22: TC Verify map integration Table 23: TC View/verify kiosks on map Table 24: TC Verify correct handling of order request based on the status of the selected kiosk Table 25: Testing Schedule TPC_DCP_F18a_T05_V1.1.doc iv Version Date: 11/02/18

5 1. Introduction The purpose of testing for this project is to verify that the developed mobile application satisfies the fundamental capabilities and functionalities, as agreed upon with the client, for both ios and Android, but with an ios development focus. Since this app is being created from scratch, there are no existing requirements or test plan cases in place to maintain during development. The scope of testing is based on the use cases that have been identified to satisfy the project s agreed-upon Win condition requirements for the ust Have operational capabilities. The focus of testing will be verifying these use cases. The type of testing will be functionality testing for each of the implemented use cases and verifying their robustness for each viable entry and/or exit scenario. 1

6 2. Test Strategy and Preparation We will utilize multiple strategies when it comes to testing our software. We will of course utilize the agile methodology of testing which involves adjusting our plans as new information emerges. However, to start with, we will test with an established test of test cases presented within this document. We will test each one of the cases weekly- even prior to a component being completed as common in test-driven agile where nonfinished tasks simply fail the test. As development continues and more code is completed, testing will evolve to potentially focus more deeply on areas of concern of the application that require the additional attention. Test prioritization will be based on our key use cases as agreed upon by the client and the team. Areas that show less reliability when testing begins can potentially be prioritized for additional tests. Our testing will also be adjusted based on the feedback of the members of the project team and the client. 2.1 Hardware preparation We do not require any hardware preparation for testing as we can and will test on simulators. However, in the future as this is a mobile application, we may decide to test on an iphone X, which one of our teammates has prepared and used for testing applications on in the past. 2.2 Software preparation The majority of our software preparations ensures that we have the correct software tools such as test simulators and test libraries. However, certain considerations will be need to accounted for within the code itself to ensure that automated tests are able to run. For example, software UI elements such as a particular button should have a unique identifier so that an automated UI testing tool such as Detox React Native are able to properly crawl through the user flows. Additional considerations will be encountered as testing begins. 1. Xcode for ios simulator: 2. Android Studio for Android simulator: 3. Open projects with Native code: 4. Detox React Native testing library: 2

7 Third party libraries Other pre-test preparations Pre-anual Testing Set Up Identify important use cases and define them as a test suite Create manual test cases that test each set of individual actions within the important test cases and document the steps and expected outcomes. anual Tests can be documented via any collaboration tool such as Google Sheets, such a tool should be set up and ready for use before testing begins. 2.4 Requirements Table 1: Requirements atrix Test Case Test Description Sub Test Case Sub Test Case Description Verification Type Requirement ID TC-01 Sign-up TC Validate user input Testing WC_4981 TC Create user account Testing WC_4981 TC Verify user account creation in DB Inspection WC_4981 TC-02 Login/Logout TC Verify Facebook login integration Testing WC_4981 TC Verify user login input Testing WC_4981 TC Verify user login in DB Inspection WC_4981 3

8 TC Verify user logout in DB Inspection WC_4981 TC-03 Browse recipes TC View recipes - Order page Inspection WC_4820 TC View recipes - Recipes page Inspection WC_4820 TC Recipe saved - Verify displayed recipes against DB Testing/Inspection WC_4820 TC Recipe deleted - Verify displayed recipes against DB Testing/Inspection WC_4820 TC Recipe selected (Order page) - Verify available recipe actions Testing WC_4919 TC Recipe selected (Recipes page) - Verify available recipe actions Testing WC_4919 TC-04 Saving/deleting recipes TC Save recipe Testing/Inspection WC_4835 TC Delete recipe Testing/Inspection WC_4835 TC-05 Customizing recipes TC Verify ingredient levels can be modified from base recipe Testing WC_4846/ WC_4918 TC Verify customized recipes can be modified Testing WC_4982 TC Verify Recipe Review modifications and actual recipe modifications match Testing/Inspection WC_4846/ WC_4918 TC Verify DB updates Inspection WC_4846/ WC_4918 TC-06 Sharing recipes via social media TC Verify/validate recipe sharing function and results (share to Facebook account) Testing/Inspection WC_4909 4

9 TC-07 Searching/ TC Verify map integration Inspection WC_4916/ selecting kiosks WC_4983 TC View/verify kiosks on map Simulation/ Inspection WC_4916/ WC_4983 TC Verify correct handling of order request based on the status of the selected kiosk Testing WC_4916/ WC_ Test Identification 3.1 Test Identifier TC-01: Sign-up 5

10 3.1.1 Test Level Software item level Test Class Usability testing Test Completion Criteria The test for sign-up will be completed when Sign-up requests are only considered valid if submitted with non-blank username and password field. Valid sign-up requests only create a new user account if the username input is unique; otherwise, an error message is displayed. New user accounts are verified as added to the user database Test Cases Table 2: TC Validate user input Input TC Validate user input Username and password must both be filled in order to proceed to authentication step User submits Sign-up form If input is valid, proceed to query DB for username availability; else, display error message. User submits Sign-up form with one of the following input types: 1. Username: sally1, Password: <blank> 2. Username: <blank>, Password: Username: <blank>, Password: <blank> 4. Username: sally1, Password: 123 If user input is of type 1-3, display error message for 6

11 missing form information. If user input is of type 4, check if given username is available for account creation. User input error. WC_4981 Table 3: TC Create user account TC Create user account If a sign-up request is valid, the username will be queried in the user database. If no results returned, create user account; else, display error message. User submits Sign-up form with valid input. Depending on user DB query results, create a new user account or not. Input Username input can be one of the following: 1. Not associated with existing account 2. Associated with existing account If user input is type 1, new account will be created; else if user input is type 2, error message will display. 7

12 Assumes user is trying to create a new account and not to log in to an existing account. WC_4981 Table 4: TC Verify user account creation in DB TC Verify user account creation in DB Ensuring that new user account can be viewed in the user DB. A new user account is created. Input If a new user account has been created, it can be verified to exist in the user DB. WC_4981 8

13 3.2 Test Identifier TC-02: Login/Logout Test Level Software item level Test Class Usability testing Test Completion Criteria The test for login/logout will be completed when App login request only proceeds to user s app homepage if valid username/password info is provided (i.e. valid Facebook login or user info found in user DB). App login/logout activity can be verified in the DB Test Cases Table 5: TC Verify Facebook login integration TC Verify Facebook login integration Verify integration of Facebook login User submits FB login info to access app. User is logged into app via FB. 9

14 Input User submits FB login info. For valid FB login submission, user proceeds to app homepage. Assumes user has FB account. WC_4981 Table 6: TC Verify user login input TC Verify user login input Login info submitted is queried in user DB to determine whether to proceed to app homepage or display error message User submits username/password information. If login info has been verified to be associated with an existing account, proceed to app homepage; else, display error message. 10

15 Input Non-blank username/password login info. If query of username/password combination finds an existing account, proceed into that user account s homepage; else, return an error. Assumes user submits with non-blank username/password combo. Otherwise, refer to TC WC_4981 Table 7: TC Verify user login in DB TC Verify user login in DB Verify successful user login is reflected in DB User successfully logs in to app. Input 11

16 If a user account is logged in, it should be indicated as active in the DB. WC_4981 Table 8: TC Verify user logout in DB TC Verify user logout in DB Verify successful user logout is reflected in DB User successfully logs out of app. Input If a user account is logged out, it should be indicated as inactive in the DB. 12

17 WC_ Test Identifier TC-03: Browse recipes Test Level Software item level Test Class Usability testing Test Completion Criteria The test for browse recipes will be completed when Recipes are correctly displayed for each recipe browsing method (i.e. Recipes page, Order page). All actions that can be performed on a selected recipe are verified, depending on the browsing method. The list of browsable recipes are correctly updated when recipes are added to or deleted from the DB Test Cases Table 9: TC View recipes - Order page TC View recipes - Order page View customized and base recipes via the 13

18 Order page Input User selects Order option from menu Order page selected. Customized recipes and base recipes will be displayed Actual results should match expected results. WC_4820 Table 10: TC View recipes Recipes page Input TC View recipes - Order page View customized recipes via the Recipes page User selects Recipes option from menu Recipes page selected. Customized recipes will be displayed 14

19 WC_4820 Table 11: TC Recipe saved - Verify displayed recipes against DB Input TC Recipe saved - Verify displayed recipes against DB Verify that browsable recipes update appropriately when new recipes are added. A new recipe is added to the DB. Saved recipe will be added recipe DB. Updated list of browsable recipes for both Order and Recipes pages. The new recipe will be included in the recipes listed on both the Order and Recipes page. WC_4820 Table 12: TC Recipe deleted - Verify displayed recipes against DB TC Recipe deleted - Verify displayed recipes against 15

20 DB Input Verify that browsable recipes update appropriately when recipes are removed. A recipe is deleted from the DB. Deleted recipe will be removed recipe DB. Updated list of browsable recipes for both Order and Recipes pages. The deleted recipe will be no longer be included in the recipes listed on both the Order and Recipes page. WC_4820 Table 13: TC Recipe selected (Order page) - Verify available recipe actions Input TC Recipe selected (Order page) - Verify available recipe actions Verify that a recipe selected from the order page cannot be shared, modified, or deleted. They can only be ordered from this view. User selects recipe from Order page. Order page selected. 16

21 ake sure the UI does not allow recipes selected from the Order page to be shared, modified, or deleted. WC_4820 Table 14: TC Recipe selected (Recipes page) - Verify available recipe actions Input TC Recipe selected (Recipes page) - Verify available recipe actions Verify that a recipe selected from the Recipes page can be shared, modified, and deleted. User selects recipe from Recipes page. Recipes page selected. ake sure the UI allows recipes selected from the Recipes page to be shared, modified, and deleted. WC_

22 3.4 Test Identifier TC-04: Saving/deleting recipes Test Level Software item level Test Class Usability testing Test Completion Criteria The test for saving/deleting recipes will be completed when The recipe DB is correctly updated when recipes are added or deleted Test Cases Table 15: TC Save recipe Input TC Save recipe A recipe save request will result in a new recipe added to the recipe DB User selects to save a recipe from the Customization page. Recipe DB is updated with new recipe. Saved recipe will appear in user s Recipes and Order page. User selects to save a recipe from the Customization page. Saved recipe will be added to the recipe DB and appear in user s Recipes and Order page. 18

23 WC_4835 Table 16: TC Delete recipe Test Case Number Input TC Delete recipe A recipe delete request will result in the associated recipe being removed from the recipe DB User selects to delete a recipe from the Customization or Recipes page. Recipe DB is updated to remove the recipe. Deleted recipe will no longer appear in user s Recipes and Order page. User selects to delete a recipe from the Customization or Recipes page. Deleted recipe will be removed from the recipe DB and no longer appear in user s Recipes and Order page. WC_

24 3.5 Test Identifier TC-05: Customizing recipes Test Level Software item level Test Class Usability testing Test Completion Criteria The test for customizing recipes will be completed when Customized recipes that have been saved and/or ordered can be verified in the DB. Recipes can be modified and saved only from certain recipe viewing pages Test Cases Table 17: TC Verify ingredient levels can be modified from base recipe Input TC Verify ingredient levels can be modified from base recipe ake sure that ingredient levels can be modified from a starting recipe. User selects to modify existing recipe from Recipes page or selects recipe from Customization page. When customization is complete, Recipe Review page appears to show selected customizations. Options to save, order, etc may be available from this page. User selects to modify existing recipe from Recipes page or selects recipe from Customization page. The UI should allow the user to modify the amounts of the available ingredients via sliders and buttons. 20

25 Assumes base and/or previously saved recipes exist. WC_4846/WC_4918 Table 18: TC Verify customized recipes can be modified TC Verify customized recipes can be modified ake sure customized recipes can be modified from the Recipes page (and NOT from the Order page) User selects a recipe from either the: (1) Recipes page (2) Order page Input If the user selects a recipe through (1), they should be able to modify and save the recipe. Else, if a recipe is selected through (2), they should only be able to view the recipe and no modifications can be made. A recipe selected from the Recipes page can be modified and either overwrite the existing recipe or be saved as a new recipe. 21

26 WC_4982 Table 19: TC Verify Recipe Review modifications and actual recipe modifications match Input TC Verify Recipe Review modifications and actual recipe modifications match ake sure customization selections and Recipe Review page values match User has finished customization and is now viewing Recipe Review page. Customization selections made and selections shown on Recipe Review page should match. WC_4846/WC_4918 Table 20: TC Verify DB updates TC Verify DB updates ake sure customized recipe/order is correctly updated in the DB 22

27 Input User has chosen to save and/or order their customized recipe. Customized recipe should be found in the DB. Saved/ordered customized recipe should be found in the DB. User has chosen to save/order customized recipe. WC_4846/WC_ Test Identifier TC-06: Sharing recipes via social media Test Level Software item level Test Class Usability testing Test Completion Criteria The test for customizing recipes will be completed when Recipes can be shared, viewed, and accessed via social media sites. 23

28 3.6.4 Test Cases Table 21: TC Verify recipe sharing function (share to Facebook account) Input TC Verify recipe sharing function (share to Facebook account) Verify that a recipe can be successfully shared to Facebook and that the data is valid User selects to share a recipe. Shared recipe notification should appear on FB account the recipe was shared to. User selects recipe to share and may or may not add a message as well. The shared recipe will be posted to the Facebook account the recipe was shared to. If a message was added, the message should also appear in the post. WC_

29 3.7 Test Identifier TC-07: Searching/selecting kiosks Test Level Software item level Test Class Usability testing Test Completion Criteria The test for searching/selecting kiosks will be completed when Kiosks are correctly displayed on map based on either user s GPS location or requested search area. A kiosk can only be successfully used for an order if the kiosk is listed as available Test Cases Table 22: TC Verify map integration Input TC Verify map integration Verify that the Google aps API has been successfully integrated into app. User selects option to pick a kiosk to submit an order to. Google map appears, centered at user s current GPS location. User selects Choose a kiosk to pick up option Google map successfully appears, centered at user s current GPS location. 25

30 WC_4916/ WC_4983 Table 23: TC View/verify kiosks on map Input TC View/verify kiosks on map Verify kiosks can be displayed on top of map and that they are accurate User selects Choose a kiosk to pick up option Google map appears and kiosks within that map location with be displayed User selects Choose a kiosk to pick up option Google map appears with viewable kiosk icons on top. Displayed kiosks should be validated against the kiosk DB. TC passes. WC_4916/ WC_

31 Table 24: TC Verify correct handling of order request based on the status of the selected kiosk Input TC Verify correct handling of order request based on the status of the selected kiosk Verify that only kiosk s with status ON can be used for order submissions User selects a kiosk from map display to complete his/her order. If the selected kiosk is ON, proceed with order process; else, display error message. Kiosk is selected from map view. If the selected kiosk is ON, proceed with order process; else, display error message. TC and TC pass. WC_4916/ WC_

32 4. Resources and schedule Our team has two distance students who will perform IV&V activities on the project and its components including documentation, the code that is developed, and the UX flow of the application. Our testing schedule will be based on the cadence of project progress; whenever a document is updated or completed or whenever a new milestone regarding the project development itself is completed, testing will occur. Testing and IV&V activities will be considered an essential part of the process; the results of these activities will help set or adjust the goals for future project milestones. The time allotted for testing weekly will be equivalent to the agreed and signed upon commitment to the class and the project and will be equal to the efforts put forward by development and other similar tasks. 4.1 Resources Our basic needs for testing require the usage of Android and ios simulators to ensure that the software is working as intended and that the use cases required are being satisfied. Below, the additional resources for testing the software product are listed: Test data sets for: Kiosk locations Free collection of Los Angeles Starbucks locations available online for testing Basic coffee recipes Free online recipes available for use, e.g. User logins (Optional) User payment information Will either need to utilize sandbox from payment provider or test by mocking. User social media logins Against Facebook TOS to create fake accounts, will need to test with real user accounts. Detox React Native Testing Software for running automated UI and acceptance tests for React Native applications Free to use, available on Github Google Sheets for anual Testing Free to use, requires some upfront set-up to make it function comparably to other manual testing tools. 28

33 4.2 Staffing and Training Needs We will require at least one dedicated team member to perform IV&V tasks including testing. The responsibilities for testing including managing, preparing, executing, witnessing, inspecting, and resolving test items Currently, the two project members committed to performing IV&V tasks are: Kate Glazko Chloe Good The rest of the project team will provide the artifacts to be tested/verified. In order to test the project thoroughly, our IV&V will need to have skills in: Analysis of documents Git (to download latest software) ios or Android simulators Writing manual test suites Writing automated test suites for React Native Our IV&V team have significant industry experience as software testers and are skilled in Git, and one IV&V has background experience with mobile simulation, writing manual test suites, and writing automated tests. Training needs mainly relate to automated testing of React Native projects; learning how to use a library such as Detox will require some learning for both IV&V members. 4.3 Schedule Table 25: Testing Schedule Date Test Identifier Responsible person Resources Training needs 10/26/18 TC TC Kate Glazko Google Sheets N/A, will run tests manually 11/02/18 TC TC Kate Glazko Detox React Native, Google Sheets Detox RN set-up, will do tutorials 11/09/18 TC TC Chloe Good Google Sheets N/A, will verify manually 11/16/18 TC TC Kate Glazko Detox RN, Google Sheets 11/23/18 TC TC Kate Glazko Detox RN, Google Sheets N/A N/A 29