Test Plan and Cases (TPC) s1

Test Plan and Cases (TPC)

Lose4Good.org Database Driven Socially Connected Website

Team 08

Team Member Name Primary Role Secondary Role Ali Alotaibi Requirements Engineer System Architect Ankit Kalwar Operational Concept Engineer Project Manager Arul Samuel System Architect Requirements Engineer Manas Jog Prototyper Requirements Engineer Monil Ashok Parikh Quality Focal Point System Architect Omkar Yerunkar Project Manager Feasibility Analyst Shalini Srinivas Feasibility Analyst Life cycle planner Test Plan and Cases (TPC) Version 1.2

Version no x.xx

<11/24/2013>

0b883c461eac624b873a8a891676403c.doc ii Version Date: 11/24/2013 Test Plan and Cases (TPC) Version 1.2

Version no x.xx Version History Date Auth Versio Changes made Rationale or n 11/16/1 Shalin 1.0  Original template  First draft with test cases 3 , Ali definition 11/23/1 Shalin 1.1  Sections 1&3 completed  Second draft for ARB 3 i

0b883c461eac624b873a8a891676403c.doc iii Version Date: 11/24/2013 Test Plan and Cases (TPC) Version 1.2

Version no x.xx Table of Contents

TEST PLAN AND CASES (TPC)...... I

VERSION HISTORY...... III

TABLE OF CONTENTS...... IV

TABLE OF TABLES...... V

TABLE OF FIGURES...... VI 1. Introduction...... 7 2. Test Strategy and Preparation...... 8 2.1 Hardware preparation...... 8 2.2 Software preparation...... 8 2.3 Other pre-test preparations...... 8 2.4 Requirements Traceability...... 8 3. Test Identification...... 8 3.1 Test Identifier...... Error! Bookmark not defined. 3.2 Test Identifier...... Error! Bookmark not defined. 4. Resources and schedule...... 19 4.1 Resources...... 19 4.2 Staffing and Training Needs...... 19 4.3 Schedule...... 19

0b883c461eac624b873a8a891676403c.doc iv Version Date: 11/24/2013 Test Plan and Cases (TPC) Version 1.2

Version no x.xx Table of Tables

Table 1: Requirements Traceability Matrix...... Error! Bookmark not defined. Table 2: TC-01-01 Check report completeness...... 9 Table 3: TC-01-02 Check report correctness...... 17 Table 4: Testing Schedule...... 19

0b883c461eac624b873a8a891676403c.doc v Version Date: 11/24/2013 Test Plan and Cases (TPC) Version 1.2

Version no x.xx Table of Figures

Figure 1:

0b883c461eac624b873a8a891676403c.doc vi Version Date: 11/24/2013 Test Plan and Cases (TPC) Template Version 1.2

A.1. Introduction

1.1 Purpose of the TPC

The purpose of this document is to describe the scope, approach, resources, and schedule of testing the hardware, software, and requirements for the services provided for Lose4Good organization.

1.2 Status of the TPC

This version includes completions of section 1 and 3. Section 1 details the purpose, scope and focus of testing for the project. Section 3 describes the test cases in detail.

1.3 Purpose for Testing

Software testing is a necessary means for finding and mitigating defects, inconsistencies, and ambiguities in documentation and code. The purpose of this Test Plan and Cases document is to capture and track the planned and implemented testing plan and the test cases to be used during the Team 08 CSCI577 project.

Our test cases will focus on the key aspects of the project, primarily the system functionality, the flow of the components and the user interface. Testing will include execution of portions of the software with inputs designed to solicit specific responses. Those responses will be evaluated to ensure the code is functioning as desired.

1.4 Scope

Testing will commence during the second semester in the Development phase. The scope of the testing will include verification of the requirements in different stages of the product development iteration. It also includes security aspects of the software components and defect detection strategies.

1.5 Focus

Our test cases will focus on the key aspects of the project, primarily the system functionality, the flow of the components and the user interface. Testing will include execution of portions of the software with inputs designed to solicit specific responses. Those responses will be evaluated to ensure the code is functioning as desired.

0b883c461eac624b873a8a891676403c.doc 7 Version Date: 11/24/2013 Test Plan and Cases (TPC) Template Version 1.2

A.2. Test Strategy and Preparation

TBD A.2.1 Hardware preparation

TBD A.2.2 Software preparation

TBD A.2.3 Other pre-test preparations

TBD A.2.4 Requirements Traceability

TBD A.3. Test Identification

All test cases in this section have the assumption that the user has internet access and the Lose4Good site is online with no hosting problems.

A.3.1 TC - 01 Login/Logout and Registration

Test case 1 covers successful and unsuccessful login, logout and registration test cases.

.3.1.1 Test Level

Software Item Level

.3.1.2 Test Class

Functionality Test

Erroneous Test

.3.1.3 Test Completion Criteria

 The system will allow the user to login with a valid username and password.  The system allows the user to login using Facebook credentials.  The system allows the user to register his/her details.  User with valid credentials is able to see the home page on successful login.  The system will display an error message to the user when incorrect login information is provided.  The system will remember the user session until the user logs out.  The system ends the session on the click of the logout button.

.3.1.4 Test Cases

Table 1: TC-01-01 Verify successful Login

Test Case Number TC -01-01 Verify successful login Test Item Test successful login to the system with a valid username and password Test Priority Must have Pre-conditions - User has already created a username and password. - User has navigated to the Login Interface.

Post-conditions - The system maintains the user login information for the remainder of the session. - The system allows the user to access the website. Input Specifications User will attempt to login to the website using valid username and password.

Expected Output Specifications System forwards user to the site homepage. Pass/Fail Criteria Pass criteria - Verify that the system allows the user to go to the homepage with successful login credentials. Fail criteria - If the pass criteria is not met. Assumptions and Constraints None Dependencies None Traceability WC_2713

Table 1: TC-01-02 Verify successful Login using Facebook credentials

Test Case Number TC -01-02 Verify successful login using Facebook credentials Test Item Test successful login to the system with Facebook username and password. Test Priority Must have Pre-conditions - User already has a Facebook account. - User has navigated to the Login Interface.

Post-conditions - The system maintains the user login information for the remainder of the session. - The system allows the user to access the website. Input Specifications User will attempt to login to the website using the account holder's Facebook information. Expected Output Specifications System forwards user to the site homepage.

Pass/Fail Criteria Pass criteria - Verify that if the user is already logged into Facebook, the system uses the Facebook credentials. - If not, the system takes the user to the Facebook login page and allows the user to enter his credentials. - The system allows the user to login to the system with his/her Facebook login information and allows the user to go to the homepage. Fail criteria - If the pass criteria are not met. Assumptions and Constraints None Dependencies None Traceability WC_2576

Table 3: TC-01-03 Verify unsuccessful Login

Test Case Number TC -01-03 Verify unsuccessful login Test Item Test unsuccessful login to the system with invalid username and password. Test Priority Must have Pre-conditions - User has navigated to the Login Interface.

Post-conditions System operational state. Input Specifications User will attempt to login to the website using invalid username and/or password. Expected Output Specifications The system displays an error message "Invalid login. Username and password does not match" and redisplays the login screen. Pass/Fail Criteria Pass criteria - Verify that the system does not allow the user to go to the homepage with unsuccessful login credentials. Fail criteria - If the pass criteria is not met. Assumptions and Constraints There have been < 3 unsuccessful logins using the username in the last 60 minutes.

Dependencies None Traceability WC_2713

Table 4: TC-01-04 Verify successful registration

Test Case Number TC -01-04 Verify successful registration Test Item Test successful registration with the system with valid name, email address, date of birth, user name and password details. Test Priority Must have Pre-conditions - User has navigated to the Login Interface.

Post-conditions - System allows the user to login using the newly created username and password. - System stores the user information into the database. Input Specifications User will attempt to register name, email address, date of birth, gender, username and password into the system. Expected Output Specifications The system displays a message "Successfully created a username and password". Pass/Fail Criteria Pass criteria - Verify that the system allows the user to enter his name, email address, date of birth, gender, user name and password. Fail criteria - If the pass criteria is not met. Assumptions and Constraints None

Dependencies None

Traceability WC_2521 A.3.2 Test Identifier

Goal Creation

.3.2.1 Test Level

Software item level

.3.2.2 Test Class

Functionality test

Erroneous test

 When Create Goal link is clicked, the system should redirect the user to Create Goal web page.  The system should not allow the weight-loser to enter more than 25 lbs.  When the user confirms the goal details, the system should allow the user to enter the sponsor's information.  The system creates the goal successfully on the click of the 'SUBMIT' button

.3.2.4 Test Cases

Table 5: TC-02-01 Verify successful goal creation

Test Case Number TC -02-01 Verify successful goal creation Test Item Test successful goal creation. Test Priority Must have Pre-conditions - User has navigated to the Create Goal page. Post-conditions System stores the goal information into the database. Input Specifications User will specify his current height and weight, target weight to lose and the target date. Expected Output Specifications The system displays a message "Goal successfully created". Pass/Fail Criteria Pass criteria - Verify that the system allows the user to enter his current height and weight, target weight to lose and the target date. - When the target weight is more than 25lbs, the system displays an alert message "Target weight limit is 25 lbs". Fail criteria - If the pass criteria is not met. Assumptions and Constraints The user is new to the system. If not, the user has completed his previous goal. Dependencies None Traceability WC_2715

A.3.3 Test Identifier

Goal tracking

.3.3.1 Test Level

Software item level

.3.3.2 Test Class

Functionality test

Erroneous test

 The system should display the progress report of the goal to the user on the click of the 'Progress' tab in the homepage.

.3.3.4 Test Cases

Table 6: TC-03-01 Verify goal tracking

Test Case Number TC -03-01 Verify goal tracking Test Item This item will test the user ability to track his/her goal and being able to view the details of his progress via charts and graphs Test Priority Must have Pre-conditions - User has navigated to the Progress page - User has already created a goal. Post-conditions None Input Specifications User's goal details Expected Output Specifications The system displays the goal progress in the form of charts along with message about the status of weight updation. Pass/Fail Criteria Pass criteria: - The system displays the user’s current and previous weight in the form of a pie chart. - The system shows a progress bar for a period of one month. - The system displays the amount of money pledged and the amount sent to charity Fail Criteria: - Any fail in pass criteria. - Mismatch in the users weight displayed and entered. Assumptions and Constraints The user is new to the system. If not, the user has completed his previous goal. Dependencies TC-02 Traceability WC_2518

Weight Updating

.3.4.1 Test Level

Software item level

.3.4.2 Test Class

Functionality test

Erroneous test

 The system redirects to update weight page when the user clicks on 'UpdateWeight' button.  The system should allow the user to upload the weight attestation form.  Based on the weight updated, the system should calculate the remaining lbs to lose and display the progress chart when the user clicks the progress tab.  The system should update the weight on confirming with the user and go back to home page.

.3.4.4 Test Cases

Table 7: TC-04-01 Verify weight updating

Test Case Number TC-04-01 Verify weight updating Test Item The test case will check for correct weight updating into the database by the system. Test Priority M (Must have) Pre-conditions The user has already created the goal. Post-conditions The system updates the goal details into the database for the weight loser. Input Specifications User's goal details. Expected Output Specifications The system updates the weight after confirming with the user. Pass/Fail Criteria Pass Criteria: - The system should allow the user to upload the weight attestation form. - The system should calculate the remaining pounds to lose and update it into the database after conforming it with the user. Fail criteria: Any fail in the pass criteria. - If the system allows the user to update the weight without the upload of the attestation form. Assumptions and Constraints None Dependencies TC-02 Traceability WC_2831

Achieve/Delete Goal

.3.5.1 Test Level

Software item level

.3.5.2 Test Class

Functionality test

Erroneous test

 The system should compare the user's current weight and target weight and display a congratulatory message if the target weight is achieved.  The system should allow the user to share the congratulatory message on Facebook if he wishes to share it.  On clicking the 'Share' button, the system should authorize the user to access his profile and allow the user to post the message.  The system should display a conformation message to the user after posting the message on Facebook.  The system should allow the user to delete the goal only if the sponsor is not added to the goal.  The system deletes the goal information on the click of the 'Delete Goal' button.

.3.5.4 Test Cases

Table 8: TC-05-01 Verify achieve Goal

Test Case Number TC-05-01 Verify achieve goal Test Item The test case will check for goal completion for the target goal and within the target date. Test Priority M (Must have) Pre-conditions The user has already updated his goal. Post-conditions The system automatically updates the goal status to completion in the database and allows the user to create a new goal. Input Specifications User's goal details. Expected Output Specifications The system displays a congratulatory message if the target goal is achieved and allows the user to share the message on Facebook if he wishes. Pass/Fail Criteria Pass Criteria: - The system compares the user's current and the target goal. - The system should display a congratulatory message of the goals matches. - The system should ask the user to share the message on Facebook.

- The system should connect to Facebook using the user's login details and allow the user to share the message on Facebook. Fail criteria: Any fail in the pass criteria. Assumptions and Constraints The user has a Facebook account. Dependencies TC-04 Traceability WC_2571, WC_2523

Table 9: TC-05-02 Verify delete Goal

Test Case Number TC-05-02 Verify delete goal Test Item The test case will check if a goal can be deleted and allows the user to delete the goal if it can be deleted. Test Priority M (Must have) Pre-conditions The user has navigated to the Progress page. Post-conditions The system deletes the goal details from the database. Input Specifications User's goal details. Expected Output Specifications The system deletes the goal from the database and displays a message to the user if the goal has no sponsor. If it has a sponsor, it displays an alert message "The goal cannot be deleted". Pass/Fail Criteria Pass Criteria: - The system should check if the goal has no sponsor. - If the goal to be deleted has no sponsor, it deletes the goal details from the database and should display the message "Goal deleted". - If the goal has a sponsor, the system should display a alert message "Goal cannot be deleted". Fail criteria: - The system deletes the goal if the goal has a sponsor. - Any fail in the pass criteria. Assumptions and Constraints The user has created the goal. Dependencies TC-03 Traceability WC_2716

Sponsor's Invitation

.3.6.1 Test Level

Software item level

.3.6.2 Test Class

Functionality test

Erroneous test

 The system should redirect the user to the invite sponsor page when he clicks on  The system should allow the user to add sponsor's name and email address  The system should generate an invitation link to be sent to the sponsor.  The system should generate an invitation message to the sponsor.  The system should allow the user to verify the email address and the message.  The system should send a mail to the sponsor using the entered email address with an invitation message and link.

.3.6.4 Test Cases

Table 10: TC-06-01 Verify sponsor's invitation

Test Case Number TC-06-01 Verify sponsor's invitation Test Item The test case will check if the system can send an email with the encrypted link to the sponsor when the user clicks on the Invite sponsor link Test Priority Can have Pre-conditions The user has navigated to the add sponsors page. Post-conditions The system sends an email with the encrypted link to the sponsor. Input Specifications Sponsor's details Expected Output Specifications The system should send a mail to the sponsor using the entered email address with an invitation link and an encrypted link. Pass/Fail Criteria Pass Criteria: - When the user clicks on the Invite sponsor's link, the system should redirect him to the invite sponsor's page. - The system should allow the user to edit the default message. - The system should generate an encrypted link and send it to the sponsor's email address when the clicks the conform button. Fail criteria: Any fail in the pass criteria. Assumptions and Constraints None Dependencies None Traceability WC_2520

Monitor Payment

.3.7.1 Test Level

Software item level

.3.7.2 Test Class

Functionality test

Erroneous test

 The system generates a detailed report on pending and invalid transactions.  The system allows the financial officer to approve/deny transactions.  The system sends mails to charity/sponsor about the status of transactions.

.3.7.4 Test Cases

Table 11: TC-07-01 Monitor payment for a valid transaction

Test Case Number TC-07-01 Monitor Payment for a valid transaction Test Item This item will test the financial officer ability to track and monitor payment done in a given month and approve the valid ones Test Priority M (Must have) Pre-conditions Sponsor has pledged money to the charity and the user has achieved his goal. Post-conditions Pending payments are approved and money is sent to charity or refunded to sponsors Input Specifications A report of all the pending transactions (of achieved and unachieved goals) of that month. Expected Output Specifications A detailed report of the transactions completed that month. Pass/Fail Criteria Pass Criteria: - The system generates a detailed report of the pending transactions for that particular month when the financial officer goes to the reports page. - The system allows the financial officer to approve/deny the transactions. - When a transaction is approved, the system sends transaction details via email to that particular charity. - When the financial officer denies a transaction, the system initiates an automatic refund to the sponsor through PayPal. Fail criteria: Any fail in the pass criteria.

Assumptions and Constraints There are pending transactions. PAYPAL is online and connected with our website. Email addresses of charity are available in the system. Dependencies None Traceability WC_2587

Table 12: TC-07-02 Verify invalid transaction

Test Case Number TC-07-02 Verify invalid transaction Test Item The test case will check for invalid transactions and report it to the financial officer. Test Priority M (Must have) Pre-conditions Financial officer has approved a transaction or a refund is initiated. Post-conditions Invalid transaction details will be deleted from the database. Input Specifications A report of invalid transactions. Expected Output Specifications Remove the transaction from the pending list and send a warning to the user.

Pass/Fail Criteria Pass Criteria: - The system generates a report of invalid transactions(that did not go through) and displays it to the financial officer. - The system removes the transaction from the pending transaction list. - The system sends a warning mail to the user. Fail criteria: Any fail in the pass criteria.

Assumptions and Constraints PAYPAL is online and connected with our website. Email addresses of charity are available in the system. Dependencies None Traceability WC_2587

A.4. Resources and schedule

TBD A.4.1 Resources

TBD A.4.2 Staffing and Training Needs

TBD A.4.3 Schedule

Table 2: Testing Schedule

Date Test Identifier Responsible person Resources Training needs

0b883c461eac624b873a8a891676403c.doc 19 Version Date: 11/24/2013