Test Plan and Cases (TPC)

Transcription

1 Test Plan and Cases (TPC) Construction Meeting Minutes App Team 6 Pradeep Muruganandam - Prototyper and Quality Focal Point Dennis Evans - System Architect, Project Manager Pavan Lingambudhi Seshadri Vasan - Requirements Engineer Sideok You - Feasibility Analyst Shengyi Chen - Operational Concept Engineer Nguyen Tran - IIV & V Qichen Gu Life Cycle Planner 12/6/2015

2 Version History Date Author Version Changes made Rationale 11/28/15 NT 1.0 Initial commitment to create TPC document Provided testing strategy and test cases 11/30/15 NT 1.1 Added some new test cases Finalize all testing procedures and test cases Better explanation and links between test cases Edited a few existing test cases 12/1/2015 NT 1.2 Added 1 more test case Finalize test cases 12/6/2015 NT 1.3 Edited test schedule Feedback from DCR ARB presentation ii

3 Table of Contents TEST PLAN AND CASES (TPC)... I VERSION HISTORY... II TABLE OF CONTENTS... III 1. Introduction... 4 Test Strategy and Preparation Hardware preparation Software preparation Other pre-test preparations Requirements Test Identification Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Test Identifier TC Resources and schedule Resources Staffing and Training Needs Schedule iii

4 1. Introduction The purpose of testing within our project is to ensure that all functionalities in the app work as expected in production and in all circumstances (sunny and rainy days). We hope to find those corner cases through testing so that user does not experience those bad incidents in our app. The scope of our testing is spanning from specific functions in our app to a whole integrated system. We mainly focus on software that is used to build Android app and Google App Engine integration. We want to test every single function in our app to ensure that there is no crash or no syncing issue between servers. We plan to perform unit testing on specific functions, integration testing on GAE, and system testing. We also plan to implement load testing and performance testing within our app in the future in order to ensure that our app can handle well all requests made to the server by multiple users (please note that number of users will be limited since the app is used only in-house, so this is not high priority comparing to app functionalities) Test Strategy and Preparation We will be working on developing a set of unit test cases, component tests and system test. This allows us to focus more on the functionality test cases part to have extensive testing to see if the features match needed requirements. GitHub for the code repository. Jenkins for Continuous Integration Value-based test prioritization: Have test cases covering the Minimum Marketable Features on top of the priority list of cases to be checked. Then we go for all the nonessential features to be tested. 1.1 Hardware preparation Laptops for triggering the tests using corresponding software and testing frameworks. - Macbook Air, Lenovo G50 - Testing from the Dev environments. Android Mobile Phones for testing the App during development. - Android Nexus Software preparation We mostly used emulator in Android Studio (version 6.0) for all testing. We simulate different phone screen resolutions, phone CPU types, phone memory capacities, etc. in order to cover most of common use cases from our users and client. The purpose of using the emulator is to allow us the ability to generate different phone specification without needing to acquire an actual phone. It helps save money as our client does not provide any budget. General procedure: Compile and build Java code for our app in Android Studio 4

5 Select emulator properties to be generated Hit Play button in Android Studio to run app on the chosen emulator Other tools that we use: Selendroid - The Test automation framework for native or hybrid Android apps and the mobile web. (v ) Just like how Selenium works for Web Applications, Selendroid is made for Android apps. We need to record the webpages in a record and playback way for the page ordering for a good number of iterations. Appium v1.5 - Open Source Mobile Automation framework. For testing the functionality of the mobile application - testing methods and functionalities using Android API s and controls. junit API part of the Android SDK for testing basic Java methods that don t call Android API s or controls. Apica - Load and Performance testing tool for Mobile Applications 1.3 Other pre-test preparations Run our general unit test suite for the individual java methods before we start to do full-fledged Mobile App testing and Load Testing 1.4 Requirements Table 1: Requirements Matrix Requirement ID Verification Test Case ID (if applicable) Type PR-1 Zero Monetary budget Demonstration CR-7 Backend GAE functionalities Testing TC-06 CR-1 Create new project Testing TC-07 CR-2 Create new meeting Testing TC-01 CR-3 View/Edit meeting Testing TC-02 CR-4 Generate report & Testing TC-03 CR-5 Generate and edit task list Testing TC-04 CR-6 Task comment Testing TC-05 CR-8 Signup/Edit contractor Testing TC-08 information CR-9 Login functionality Testing TC-09 5

6 2. Test Identification 2.1 Test Identifier TC1 TC-01: Create meetings Test Level Software item level Test Class Functionality test Test Completion Criteria The test case for creating a meeting will be completed when: -A privileged user is able to locally create a meeting on a new project -A privileged user creates a meeting locally on a continuation project and the system successfully rolls in pending tasks and default project attendees. -The system prevents a non-privileged user from creating a meeting. -The system prevents the meeting from being published and viewable to all users upon creation Test Cases Table 2: TC Create new meeting for new project TC Create new meeting for new project. This test case verifies that a privileged user can create a new meeting for a new project. M Manager has logged into the system as a privileged user. Manager has created a new project for which to add the new meeting to. A new meeting is created for the project with the correct category, date, meeting attendees, and task list. 1. From the project specific dashboard a manager selects new meeting. 2. Manager selects type of meeting. 3. Enter date, meeting attendees, and populate task list. 4. Select create A meeting for the project is created with the correct 6

7 Assumptions and Constraints information while returning the user to the project dashboard. Pass Criteria: -A new meeting is created that is viewable on only the manager s device until it is published. -The new meeting contains the correct inputted information. Fail Criteria: -Other than pass criteria. -A new project has been created. -The user has a privileged account. Create Project (TC-07-01) WC_3513 Table 3: TC Create new meeting for continued project TC Create new meeting for continued project. This test case verifies that project default attendees and pending tasks will be rolled in when a new meeting is created on a continuing project. M Manager has logged into the system as a privileged user. Existing project contains a meeting of the same type that the manager is about to create. A new meeting is created for the project with correct pending tasks being rolled in from previous meeting and default attendee list from project information. 1. From the project specific dashboard a manager selects new meeting. 2. Manager selects type of meeting. 3. Enter date, meeting attendees in addition to the default attendees, and add new tasks. 4. Select create After selecting the type of meeting, the create meeting page is shown with attendee list already populated from the project s default attendee list. Task list is also automatically populated with pending tasks from the previous meeting. A meeting for the project is created with the correct information that was added or automatically rolled in. Pass Criteria: -A new meeting is created that is viewable on only the manager s device until it is published. -The new meeting contains the correct inputted information along with the default attendees and pending tasks from the previous meeting of the same type. Fail Criteria: -Other than pass criteria. 7

8 Assumptions and Constraints -A project contains a default attendee list. -There already exists a meeting of the same type for the current project with tasks that are still pending. -The user has a privileged account. TC WC_3513 Table 4: TC Attempt to create new meeting as unprivileged user Assumptions and Constraints TC Attempt to create new meeting as unprivileged user. This test case verifies that a non-privileged user cannot create a meeting. M User has logged into the system as a non-privileged user. Project dashboard is displayed without the option to create a new meeting. 1. After logging on, the user selects a project. The non-privileged user is taken to the project dashboard and privileged options such as create new meeting are not shown or accessible. Pass Criteria: -Project dashboard page is shown without the new meeting functionality. Fail Criteria: -Non-privileged user has option to create a meeting. -A project has been created. Create Project (TC-07-01) WC_ Test Identifier TC2 TC View / Edit Meeting Test Level Software Item Level Test Class Functionality Test 8

9 2.2.3 Test Completion Criteria Edit (and View) Meeting scenarios will be complete when: Required meeting details are fetched and be able to view by user. Able to select a meeting for editing and enter details to edit. Able to store the edited information in the server once editing is done. View the edited meeting information by selecting the same meeting name Test Cases Table 5: TC View Right Meeting Information TC Viewing Right Meeting Information Tests whether the user with admin privileges is able to view the meeting details of the meeting selected. M - Must Have Since this feature is needed for the manager to view meeting details of what have been added to system and make changes later if necessary. So, it becomes a Must Have feature. Manager is logged in to the App. Before we test the view meeting scenario, we must make sure that the Create Project and the Create meeting test case scenario has been executed so that we have meetings in the cloud server for the project. The meeting data is not affected by this test case since it is only a read operation. The View Meeting option needs to be selected in the Dashboard page and the meeting name desired needs to be selected in the Meeting Name drop down list box. The meeting information corresponding to the meeting name selected is displayed by filling the necessary fields on the page. It is available for viewing or editing based on the user privileges. Pass Criteria : ( All needs to pass to be deemed a success) On selecting the view meeting option, goes to view meeting page. Displays correct list of meetings held for the corresponding project chosen at present. On selecting a name, should display the correct details of the meeting like Data, Attendees List, List of Minutes,etc. Fail Criteria : 9

10 Failure in 1 or more of mentioned pass criteria or any sort of unexpected behavior of the app. Assumptions and Constraints Assumptions: A project and meeting must have been created in the system before we exercise the test case. Constraints: Normal account users will not see all the meeting details but only their relevant details. So, user needs to be logged in to Administrator privilege account (Manager) to get desired output of test case. Create Meeting - TC Create Project - TC - 07 WC_3699. Table 6: TC Edit Meeting Information TC Edit Meeting Information Tests whether the user with admin privileges is able to edit the meeting details of the meeting being viewed in the view meeting page. M - Must Have This feature is mandatorily needed for the manager to edit meeting details like tasks, publish details, type of meeting, etc. So, it becomes a Must Have feature. Manager (Privileged user) is logged in to the App. Before we test the edit meeting scenario, we must make sure that the Create Project and the Create meeting test case scenario has been executed with expected results and also we are rightly fetching the meeting details via the view Meeting scenario. The meeting which is edited will now have the new set of information as keyed in during the operation. The cloud server now has the new meeting details object and it is retrieved to check. Open the View Meeting page, select a meeting. Once we have the meeting open, choose to edit. Change the name, type, location or 10

11 choose to edit the minutes or attendees. Once done, click update button. Assumptions and Constraints The meeting information changed will be update to the Google Cloud Storage and when we try to view the meeting details of the same meeting again, we can see that the meeting now carries the changed data which was inputted during the test case. Pass Criteria : ( All needs to pass to be deemed a success) View meeting on select meeting name properly. Allow to enter new details for needed fields. Save changed data to cloud storage database. Viewing data should have changes reflecting in them. Fail Criteria : Failure in 1 or more of mentioned pass criteria or any sort of unexpected behavior of the app. Assumptions: A project and meeting must have been created in the system before we exercise this test case. Constraints: Normal account users will not see all the meeting details but only their relevant details. So, user needs to be logged in to Administrator privilege account (Manager) to get desired output of test case. Create Meeting - TC - 01, Create Project - TC - 07, View Right Meeting Information - TC WC_3777 Table 7: TC Editing an earlier meeting in a category which has already had follow-up meetings TC Editing an earlier meeting in a category which has already had follow-up meetings Tests whether the user with admin privileges is able to edit the minutes of an earlier meeting in a category which has already had follow-up meetings. It should not allow the user to do changes in such meetings as the follow-up meetings have got incomplete tasks from them. M - Must Have category This feature is mandatorily to ensure that there is no changes allowed in a meeting which was concluded and that should be ensured in categories that have had follow-up meetings. So, it becomes a Must Have feature. 11

12 Manager (Privileged user) is logged in to the App. Before we test the edit earlier meeting scenario, we must make sure that the Create Project and the Create meeting test case scenario has been executed with expected results. It is needed to have some follow-up meetings in some categories. We should rightly fetch the earlier meeting details via the view Meeting scenario. Assumptions and Constraints The meeting which we tried to edit must have only the same old information that was present before the operation. The cloud server should not undergo any sort of update or write operation after the test was performed. Open the View Meeting page, select an earlier meeting in a category which has had follow-ups. Once we have the meeting open, choose to edit. Change the name, type, location or choose to edit the minutes or attendees. Once the user presses the Update button, it should check and not allow the operation to go through saying this meeting is only a read-only meeting now. ( Only last conducted meetings in a category can be edited) Pass Criteria : ( All needs to pass to be deemed a success) View meeting on select meeting name properly. Allow to enter new details for needed fields. On clicking Update, it should not permit changes saying the meeting cannot be edited as it has had follow-ups. Viewing data should not have any changes reflected in them. Fail Criteria : Failure in 1 or more of mentioned pass criteria or any sort of unexpected behavior of the app. Assumptions: A project and meeting must have been created in the system before we exercise this test case. Some category of meeting must have had follow-up meetings. Constraints: Normal account users will not see all the meeting details but only their relevant details. So, user needs to be logged in to Administrator privilege account (Manager) to get desired output of test case. Create Meeting - TC - 01, Create Project - TC - 07, View Right Meeting Information - TC WC_

13 2.3 Test Identifier TC3 TC 03 - Generate and mail reports Test Level Software Item Level Test Class Functionality Test Test Completion Criteria The test case for this function will be completed when: -The personnel presiding over meetings can enter the important points of the meeting in a specified format and create the report as a PDF. -He/she can preview the document created if he/she needs to do so before sending. -He/she can decide whether to send the reports or not to send the reports -The generated report is sent to the concerned employees from a list obtained from the database for the meetings by and they all get the report attached with the mail Test Cases Table 8: TC Enter Data and Generate Report in a specified format as a PDF TC-03-01: Enter Data and Generate Report in a specified format as a PDF This Test Case enables the user to generate a report about a particular meeting by entering the required data in a particular Format through use of text boxes to add comments and checkbuttons, radio buttons and switches to retrieve data from database for meetings to add to the report based on the choices made by clicking the said widgets M 13

14 Pre-Conditions The User Must Be logged into the Construction Meeting Minutes Application and must be the privileged user allowed to generate the report. The Meeting must be created first or must be present and the details of the meeting must be present in the database. Post-Conditions A report has been created according to a specified format in the form of a heading etc and can be previewed if need be before it is to be sent. Click on the Report Button to go to the next activity. Enter the Details using the UI elements like text boxes, check buttons and radio buttons to enter Data and then click the Generate button to create the report A Report in The PDF format has been generated and the Report and Preview Report Buttons are enabled Pass Criteria: The Report has been generated with the exact format that has been specified according to the choices made by the user. Fail Criteria: Report not generated and it is not saved in the memory of the smartphone, and you cannot see the report on clicking the preview button Assumptions & Constraints The meeting has been created or was created earlier. The user is a privileged user who can generate the report Create Meeting Test Case (TC-01) Edit Meeting Test Case (TC-02) WC-3699 Table 9: TC Preview the Generated Report to check before sending TC-03-02: Preview the Generated Report to check before sending 14

15 Pre-Conditions Post-Conditions This Test Case is to preview the document to check if the document is according the specified format and make changes to the document in the preview if need be S The Report has been created after all the data has been entered and retrieved from the database. The Report is seen on clicking the preview Report. Click the Preview Report Button to see the report A PDF report is shown in the phone for the sender to view and make required changes before it is ed Pass Criteria: An alert dialog box appears on screen to ask the user whether he/she wants to view the document A view of the document is shown if the user responds with a Yes. Fail Criteria: Anything other than the pass criteria. Assumptions & Constraints The PDF report file has been generated after the data entry by a privileged user Test Case WC-3699 Table 10: TC The Report is sent as an attachment to all employees TC-03-03: The Report is sent as an attachment to all employees This test enables the user to send the report to concerned personnel as an attachment so that they can access the report for their own analysis and appraisal. The addresses are obtained from the databases regarding the meeting attendees 15

16 Pre-Conditions Post-Conditions M The Report has to be generated by a privileged user in a specified format after data entry.the Receiver records must be present in the database The attachment is sent to each and every one in the receiver s list Button to send the to the set of users. The with the attachment is received by all the users whose s are there in the comma separated string. Pass Criteria: The attachment is sent in an to all the receivers. Fail Criteria: The attachment is not in the mail sent to the receivers. The the attachment is not sent to all the receivers (This could be due to addresses not being in the right format) Assumptions & Constraints The Report has been generated by the privileged user. The addresses in the database are in the proper format Test Case WC_ Test Identifier TC4 TC 04 - Generate and edit a task list for contractors Test Level Software Item Level Test Class Functionality Test 16

17 2.4.3 Test Completion Criteria a. Task list is properly generated for each contractor b. Contractors can edit (check/uncheck items) task list when their device is online or offline c. Changes made while offline is synced properly to the server when device becomes online d. Task list is correctly displayed on mobile device screen Test Cases Table 11: TC task list generation Test case number Test item Test priority Input specifications Expected output specifications Pass/Fail criteria TC task list generation Task list is displayed as a checklist of items. Features: a task list is correctly populated from the meeting minutes for each contractor Must have Contractors had to attend the meeting and the project manager would compile a list of to-do tasks for each contractor after meeting. Then she would create a meeting minutes in our app, insert tasks for each contractor, and then send out notification A proper task list is generated and displayed on contractor s mobile device 1. Meeting minutes 2. from project manager 1. Task list formatted in checklist style 2. Initially all checkboxes have been unchecked Pass criteria: 1. Task list is properly generated from meeting minutes for each contractor 2. Task list is properly displayed on mobile device in checklist style 3. All checkboxes are initially unchecked Assumptions and constraints Fail criteria: Other than pass criteria Contractor is already involved in a particular project and attended at least 1 meeting Project creation (TC-07) 17

18 Meeting creation (TC-01) sent from project manager (TC-03) WC_3712 Table 12: TC Task list operation while device is online Test case number Test item Test priority Input specifications Expected output specifications Pass/Fail criteria TC check and uncheck an item Items in task list are checked or unchecked allowing contractors to identify what is left to be done Must have Task list has been already generated and displayed on contractor s mobile device A checked appears next to an item which is checked by contractor 1. Task list of items Task list with items which has a checked icon next to it representing the work has been done Pass criteria: 1. Once item is checked, a check icon is appeared next to it 2. Once item is unchecked, a check icon is disappeared Fail criteria: Assumptions and constraints Other than pass criteria Task list has been already properly generated and displayed on mobile device Task list creation (TC-04-01) WC_3698 Table 13: TC Task list operation while device is offline Test case number Test item TC checked and unchecked items while device is offline Items in task list are checked or unchecked while device is offline 18

19 Test priority Input specifications Expected output specifications Pass/Fail criteria Must have Task list has been already generated and displayed on contractor s mobile device A checked appears next to an item which is checked by contractor or a checked disappears if he unchecked it. All information is synced to the server properly when device is back online to ensure consistency 1. Task list of items 2. Device is offline Task list with items which has a checked icon next to it representing that the work has been done. When device is online, all changes in task list is synced properly to server Pass criteria: 1. Once item is checked, a check icon is appeared next to it 2. Once item is unchecked, a check icon is disappeared 3. All information stored locally on the device is synced properly to server when device is back online Assumptions and constraints Fail criteria: Other than pass criteria Task list has been already properly generated and displayed on mobile device Task list creation (TC-04-01) WC_ Test Identifier TC5 TC 05 Task comment Test Level Software Item Level Test Class Functionality Test 19

20 2.5.3 Test Completion Criteria The test for approving/rejecting the comment(s) of a task will be completed when - The manager can approve or reject the comment(s) on a task. - The contractors cannot approve or reject the comment(s) on a task even if assigned with the task Test Cases Table 14: TC Task comment approved TC Task comment approved This test cases verifies that the manager can approve a comment from a contractor on a specific task. M (Must have) The user has logged in as the manager. There are at least one pending task in the system. At least one contractor has added a comment on a task. Assumptions and Constraints The manager considers the task as completed. The task is marked as completed and removed from the pending task list. The task and the relevant comment info in the database An updated pending task list without the completed task. If the completed task is removed from the pending task list, pass; otherwise, fail. The contractor only comments on an assigned task when he or she considers the assigned task is completed. A comment is equivalent to a request for task completion check. There should be at least one pending task with an unjudged comment in the database. TC-04-01, TC-04-02, TC WC_3778 Table 15: TC Task comment rejected TC Task comment rejected This test cases verifies that the manager can reject a comment from a contractor on a specific task. M (Must have) 20

21 The user has logged in as the manager. There are at least one pending task in the system. At least one contractor has added a comment on a task. Assumptions and Constraints The manager considers the task as not yet completed. The task is still pending and the pending task list remains unchanged. The task and the relevant comment info in the database The unchanged pending task list. If the task remains in the pending task list, pass; otherwise, fail. The contractor only comments on an assigned task when he or she considers the assigned task is completed. A comment is equivalent to a request for task completion check. There should be at least one pending task with an unjudged comment in the database. TC-04-01, TC-04-02, TC WC_3778 Table 16: TC Contractor cannot approve/reject a comment TC Contractor cannot approve/reject a comment This test cases verifies that contractors cannot approve or reject a comment even if assigned with the task. M (Must have) The user has logged in as a contractor. There are at least one pending task in the system. Assumptions and Constraints At least one contractor has added a comment on a task. The task is still pending and pending task list remains unchanged. The task and the relevant comment info in the database When logged in as a contractor, there are not buttons called approve or reject on the screen so the contractor cannot approve or reject a comment. If the task remains in the pending task list, pass; otherwise, fail. The contractor only comments on an assigned task when he or she considers the assigned task is completed. A comment is equivalent to a request for task completion check. There should be at least one pending task with an unjudged comment in the database. TC-04-01, TC-04-02, TC WC_

22 2.6 Test Identifier TC6 TC 06 Saving and retrieving data in Google App Engine with Communicating with Construction Meeting Minute application Test Level Software Item Level Test Class Functionality Test Test Completion Criteria The test for Saving and retrieving data in Google App Engine with communication with Construction Meeting Minute application will be completed when - Sending data from application has to be stored in database server. - Database server has to be sending correct data which is requested by application user. - All different kinds of possible inputs has to be stored or retrieved in database server Test Cases Table 17: TC Sending data from CMMA to database server with normal input TC Sending data from CMMA to database server with normal input Using normal input for sending data from CMMA to database server M ( Must Have) The application displays meeting screen Showing message to user that it is successfully stored displays correctly 1. Enter normal data into text fields. 2. Click save button The entered data can be checked in database server Pass criteria - All entered data can be shown without any cracking Failed criteria - All entered data is shown with cracking Assumptions and Constraints - Internet is working properly (no disconnection) - Database server is working N/A WC_3708 : As a contractor, I can enter reports and data correctly with simple, easy to use interfaces at any time so that people concerned get accurate information which can be accessed anytime 22

23 Table 18: TC Sending data from CMMA to database server with abnormal input TC Sending data from CMMA to database server with abnormal input Using abnormal input for sending data from CMMA to database server M ( Must Have) The application displays meeting screen Showing message to user that it is successfully stored displays correctly 1. Enter abnormal data into text fields. 2. Click save button The entered data can be checked in database server Pass criteria - All entered data can be shown without any cracking Failed criteria - All entered data is shown with cracking Assumptions and Constraints - Internet is working properly (no disconnection) - Database server is working N/A WC_3708 : As a contractor, I can enter reports and data correctly with simple, easy to use interfaces at any time so that people concerned get accurate information which can be accessed anytime Table 19 TC-06-03: Requesting data in CMMA to database server with normal input TC Requesting data in CMMA to database server with normal input Retrieving data from database server to CMMA M ( Must Have) The application displays meeting list screen The application displays retrieved data in the meeting screen 1. Click the meeting which I want to see in the meeting lists All corresponded data is shown in the meeting screen Pass criteria - The meeting screen s normal data has to same in the database server s data Failed criteria - Requested data is shown with cracking Assumptions and Constraints - Internet is working properly (no disconnection) - Database server is working TC Sending data from CMMA to database server with normal input WC_3708 : As a contractor, I can enter reports and data correctly with simple, easy to use interfaces at any time so that people concerned get accurate information which can be accessed anytime 23

24 Table 20 TC-06-04: Requesting data in CMMA to database server with abnormal input TC Requesting data in CMMA to database server with abnormal input Retrieving data from database server to CMMA M ( Must Have) The application displays meeting list screen The application displays retrieved data in the meeting screen 1. Click the meeting which I want to see in the meeting lists All corresponded data is shown in the meeting screen Pass criteria - The meeting screen s abnormal data has to same in the database server s data Failed criteria - Requested data is shown with cracking Assumptions and Constraints - Internet is working properly (no disconnection) - Database server is working TC Sending data from CMMA to database server with abnormal input WC_3708 : As a contractor, I can enter reports and data correctly with simple, easy to use interfaces at any time so that people concerned get accurate information which can be accessed anytime 2.7 Test Identifier TC7 TC-07 Create and edit new project Test Level Software Item Level Test Class Functionality Test Test Completion Criteria a. Only privileged user (project manager) can create a new project b. Only privileged user can modify the project that he/she created c. System prevents non-privileged user from creating/modifying a project 24

25 2.7.4 Test Cases Table 21 TC-07-01: Create new project TC Create a new project This test is to verify that a new project is created successfully by a privileged user M ( Must Have) Manager has successfully logged in the system A new project is created successfully 1. Manager push Create project button from the mobile UI 2. Fill out all necessary information to create a project such as project name, purpose, contact, etc. 3. Manager push Submit button to complete creating a project A new project is created and displayed on manager s dashboard Pass criteria - A new project with correct property (name, purpose, contact, etc.) is created and displayed on manager s dashboard Failed criteria - Other than pass criteria Assumptions and Constraints - Manager account has been created and stored into the database - Internet access in order to authenticate manager s credentials User login (TC-09) WC_3780 Table 22 TC-07-02: Modify an existing project TC Modify an existing project This test is to verify that a privileged user can modify an existing project M ( Must Have) 1. Manager has successfully logged in the system 2. A project has been created A project is modified successfully and all changes are properly stored in our server database 1. Manager pushes Edit project button from the mobile UI 2. Makes all changes including but not limited to changing project name, project contact, and project purpose 3. Manager pushes Submit button to complete modifying a project New changes of a project are displayed properly on manager s dashboard Pass criteria 25

26 - All new changes of a project are displayed properly on manager s dashboard - All new changes are stored correctly into our server database Failed criteria - Other than pass criteria Assumptions and Constraints - There is at least 1 existing project in manager s dashboard TC-07-01, User login (TC-09) WC_3781 Table 23 TC-07-03: Attempt to create/modify a project as unprivileged user TC attempt to create/modify a project as an unprivileged user This test is to verify that the system could detect and prevent unprivileged user from creating and/or modifying a project M ( Must Have) User has logged into the system as a non-privileged user. Project dashboard is displayed without the option to create/modify a project. After logging on, the user navigates to his/her dashboard The non-privileged user is taken to the project dashboard and privileged options such as create new project and modify an existing project are not shown or accessible. Pass criteria - Project dashboard page is shown without the project functionality. Failed criteria - Non-privileged user has option to create a project or modify an existing project. Assumptions and Constraints - User has logged successfully TC-07-01, TC-07-02, User login (TC-09) WC_3780, WC_ Test Identifier TC8 TC-08 Signup/Edit contractor information Test Level Software Item Level Test Class Functionality Test 26

27 2.8.3 Test Completion Criteria The test for Signup/Edit Contractor Information will be completed when: 1. The contractor can type and submit the signup information and see his or her request is being processed and the signup information is successfully stored at database. 2. The manager can see the request of the contractor retrieving from the database and then approve or disapprove the request which then give the contractor username and password or notify the contractor his or her request is rejected. 3. The contractor or manager can edit and change the information of a contractor and the changes will be stored at database and update every related part Test Cases Table 24 TC-08-01: Submit signup and Check the database TC Submit signup and Check the database The test case verifies if one contractor can submit his or her request of signup and the signup information is then stored at the database. M It s the first time that the contractor sign up the request and the contractor name is never submitted before. The signup information is stored at the database. Contractor types the information needed for signup and submit it. Developer checks the database about this signup information. A notification board showing to contractor says that the signup information is submitted. Developers can find the signup information storing at database successfully. The test will pass if the notification board about submitting successfully is showing and signup information is found at the database. Assumptions and Constraints No same contractor name already stored at the database before the submission of signup. TC-06 WC_3516: As a contractor, I can log in to the app so that I can see the meeting minutes Table 25 TC-08-02: Retrieve from database and approve or not approve TC Retrieve from database and approve or not approve The test case verifies if the manager can see the request retrieving from the database and approve or not approve it and distributing of username and password. M There is signup information storing at the database. Signup information pulls out from database. 27

28 Assumptions and Constraints Username and password is given to the contractor when the request is approved. Contractor got rejected accessing when the request is not approved. Manager approves or disapproves the request. Contractor got username and password or got rejected. The test will pass if the contractor got username and password when manager approves his or her request and the contractor sees a rejection notification when manager disapproves his or her request. Signup information is stored at database and can be retrieved out to manager successfully. TC-06 WC_3775: As a manager, I can approve or disapprove the request of signup from contractors. Table 26 TC-08-03: Edit contractor information and Check database and every part Assumptions and Constraints 2.9 Test Identifier TC9 TC-09 User login functionality Test Level Software Item Level TC Edit contractor information and Check database and every part The test case verifies if the manager can see the edition of contractor information do change the information stored at the database and other related part. M There is existing contractor information storing at the database. Changing of information made on the database. Other part relating to changing information got updated. Manager or contractor edits the information of some contractors. Developers check the database and every part. Information got updated at the database and every related part. The test will pass if the changing information updates the old information storing at the database and every other related part of the system. Information got edited has stored at the database already. TC-06 WC_3776: As a manager or contractor, I can edit the contractor's information and save it. 28

29 2.9.2 Test Class Functionality Test Test Completion Criteria 1. Log user in if correct credentials are given 2. Display error and prompt user to try again if credentials are not found in the database Test Cases Table 27 TC-09-01: Log user in if correct credentials are given Assumptions and Constraints TC Log user into the system if correct credentials are given Check to see if system is able to log the user in properly given the correct credentials M User types in a username and password, then press Log in button Log the user in the system Username and password User is logged into the system Pass criteria: 1. Successfully verify with the server if a username + password combination is correct 2. Log the user in the system Fail criteria: Other than pass criteria User navigates to the log in page and hit Log in button N/A WC_3513, WC_3516 Table 28 TC-09-02: Handle failed login TC Handle failed login Check to see if system can handle a failed login attempt M User types in a username and password, then press Log in button Display error message and prompt user to try to log in again Username and password Error message is displayed on screen and prompt user to try again Pass criteria: 1. Properly display error message on screen if a given username + password combination is not found in our 29

30 database 2. Prompt user to try to log in again Assumptions and Constraints Fail criteria: Other than pass criteria User navigates to the log in page and hit Log in button N/A WC_3513, WC_ Resources and schedule Two people will be working on testing the product and one off-campus student will be performing Verification and Validation 3.1 Resources Test Data Set Test Case Scenarios Software - Selendroid, Appium, JUnit,., etc. SDK - Android SDK IDE - Android Studio Budget - N/A 3.2 Staffing and Training Needs Stakeholders involved in Testing - 2 people from Project Team, off-campus student for IV&V. Client for feedback in testing. Development group provided the deliverables to be tested. We had 2 groups of developers, each having 2 people and once a module was done, got handed over to 1 tester. In parallel, the testers would have designed and planned test cases for development modules. Once delivered, they were able to execute it on them and found defects. Skills for people to be involved: JUnit skills for Unit testing Java Code. Selendroid skills for testing mobile apps, Appium skills to be acquired for testing mobile functions. Training needs: new team members in next semester are to catch up to speed with code base and understand the design 30

31 3.3 Schedule Table 29: Testing Schedule Date Test Identifier Responsible person Resources Training needs 1/11/16 Training new team Dennis, Sideok, Github code base N/A member Pavan and diagrams 1/11/16 TC-09 Dennis JUnit, test data set, Android SDK, Android Studio Understanding GAE and how to integrate with Android 1/11/16 TC-01 Pavan JUnit, test data set, Android SDK, Android Studio 1/11/16 TC-02 Sideok JUnit, test data set, Android SDK, Android Studio 2/1/16 TC-03 Pavan JUnit, test data set, Android SDK, Android Studio 2/1/16 TC-04 Sideok JUnit, test data set, Android SDK, Android Studio 2/8/16 TC-05 Sideok JUnit, test data set, Android SDK, Android Studio 2/8/16 TC-06 Pavan JUnit, test data set, Android SDK, Android Studio 2/15/16 TC-07 Sideok JUnit, test data set, Android SDK, Android Studio 2/15/16 TC-08 Pavan JUnit, test data set, Android SDK, Android Studio app N/A N/A N/A N/A N/A N/A N/A N/A Please note that the plan above is tentative subject to changes based on how fast new team members can catch up to speed and number of bugs/defects found in each test case. If there are bugs/defects found in a test case, we will need to adjust the plan accordingly in order to fix the bug and re-test. With 2 people dedicated for testing and 1 DEN student for verification and validation, we believe that we can stay within the schedule The reason that it might take quite a bit of time in the beginning because we want to account for learning curve from our new teammates and we want to ensure that the most important functionalities work perfectly before moving on to other functionalities. 31