MACtivity Test Cases Team 6 CSE 5324: Spring 2012 Khandaker Moinur Rahman Shwetha Narayan Hardik Shah Yu Xuan Zhang Sanjay Vasudeva Iyer

Transcription

1 MACtivity Test Cases Team 6 CSE 5324: Spring 2012 Khandaker Moinur Rahman Shwetha Narayan Hardik Shah Yu Xuan Zhang Sanjay Vasudeva Iyer Department of Computer Science and Engineering The University of Texas at Arlington

2 1 INTRODUCTION 1.1 PURPOSE OF THE TEST CASE DOCUMENT This Test Cases Document documents the functional requirements of the MACtivity test cases. The intended audience is the project team and testing team. This document may be shared with the TA\Instructor and other teams whose input/approval into the testing process is needed. We designed our test cases based on following modules implemented in 3 iterations: Iteration 1: 1. Login Page 2. Registration Page 3. Individual Plan Iteration 2: 1. Group Plan 2. Friend List 3. Notification Page Iteration 3: 1. Statistics Chart 2. User Profile Page 3. User Dashboard Remember, the test cases discussed in this document gives user a graphical guideline for black-box testing. They are not JUnit test cases. 2 TEST CASES SPECIFICATION 2.1 TEST CASE SCENARIO REGISTRATION Description This test case is the description of how to test registration process of MACtivity app. Preconditions The tester clicks on Register button.

3 Post Conditions When a valid full name and address combination is given by user, the screen will show user a dialog for successful registration and send an to user containing randomly generated password. Database will be updated containing information of new user. Success Scenario: A user gives full name and valid address in correct format. For this correct input, user will receive an like this confirming successful registration: Alternative Scenario: a. Input field left blank. Result: System will show an alert dialog:

4 b. Invalid Id: Result: system will show an alert dialog like following: 2.2 TEST CASE SCENARIO LOGIN Description This test case describes how to test login process

5 Preconditions The tester should have a registered account for this app. Post Conditions When a valid combination of address and password is given by user, the app will redirect user to home activity showing dashboard and bottom action bar. Success Scenario A user gives valid credentials

6 After login, user will be able to see own home screen: Alternative Scenarios: a. Invalid credentials Result: Show an alert dialog:

7 b. Input field left blank Result: Show user alert toast: 2.3 TEST CASE SCENARIO FORGOT PASSWORD

8 Description This test case describes how to test if a registered user can retrieve password back Preconditions The tester should have a registered account for this app. He clicks on forgot password link on login screen. Post Conditions When user gives a registered address, the app send an to that address containing a randomly generated password. User should be able to login using new password. Database would be updated with new password. Success Scenario Suppose, a user gives address on forgot password screen. App will show user a dialog confirming his with new password.

9 User will receive an in following format with new password: Alternative Scenarios: a. Invalid Result: App will warn user with a toast message b. field left blank Result: Show user a toast message to fill up field

10 c. Pressing cancel button Result: Redirect to login screen 2.4 TEST CASE SCENARIO RESET PASSWORD Description This test case describes how to test if a registered user can reset password. Preconditions The tester should have a registered account for this app. He clicks on Profile icon from menubar and selects Change Password tab. Post Conditions When user gives a valid old password, and valid new password twice, the app allows user to reset to new password. App shows user a toast message that password was successfully reset. Database is updated with new password.

11 Alternative Scenarios: a. Incorrect old password Result: Show a toast message that old password is incorrect b. New passwords don t agree Result: Show a toast message about mismatch

12 c. Field missing Result: Show user a toast message that required field is missing. d. Pressing Profile Tab

13 Result: Switches to profile tab 2.5 TEST CASE SCENARIO LOG OUT Description This test case describes how to test if a registered user can log out of app. Preconditions The tester should have been logged in with a registered account for this app. He clicks on Profile icon from menu bar and clicks Logout button. Post Conditions App will log out the user and redirect to login screen. 2.6 TEST CASE SCENARIO ADD FRIEND Description This test case describes how to test the process of adding friends. Preconditions The tester should have been logged in with a registered account for this app. He clicks on Friends icon from menu bar.

14 Post Conditions User will be able to add other users to own friend list after searching by id or name. Success Scenario A user wants to add a friend whose name starts with san. Typing san and clicking search button would populate list of users whose name starts with san. Clicking on a name from list would pop up a dialog showing option of sending a friend request.

15 Clicking on Add friend button would send a friend request to that user and user will see a confirmation dialog.

16 Alternative Scenario: a. Sending multiple add request to same user Result: Dialog will show that friend request already sent. b. Trying to add own as friend Result: Dialog will warn that user is trying to add himself.

17 2.7 TEST CASE SCENARIO DELETE FRIEND Description This test case describes how to test the process of deleting friends. Preconditions The tester should have been logged in with a registered account for this app. He should have at least one friend in friend list. Post Conditions User will be able to delete selected friend from friend list. Success Scenario A user wants to delete a friend. He clicks on the name of a friend from friend list. A dialog will appear to confirm deletion. User clicks ok to delete.

18 That friend will be removed from his friend list showing a confirmation. Alternative Scenario: a. User clicks on cancel Result: Delete dialog will disappear and friend list will be back. 2.8 TEST CASE SCENARIO NOTIFICATIONS Description This test case describes how to test the process showing notification and responding to them. Preconditions The tester should have been logged in with a registered account for this app. He clicks on Alerts icon from menu bar. Post Conditions User will be able to see a latest list of notifications on the screen. These notifications include someone sent/accepted friend request, or someone invited to a group activity, or someone rejected an invitation. Clicking on some notifications would require further user interaction and some notifications would disappear from list if they are no longer important. Success Scenario:

19 A user clicks on alerts icon from menu bar. He will see a list of notifications:

20 Clicking on first notification (group plan request) will direct to a screen with details of that notification and option to accept invitation. Accepting the group plan would add a new entry to dashboard for that plan Similarly from notification page, user can accept/reject friend request

21 Click on the notification would redirect to details of that request. User can accept/reject that request. 2.9 TEST CASE SCENARIO INDIVIDUAL PLAN Description This test case describes how to test the process when an individual plans for own. Preconditions The tester should have been logged in with a registered account for this app. He clicks on Plan icon from menu bar. Post Conditions User will be able to select a particular game at a particular date and time. His plan will be reflected to dashboard. Database will update this new plan.

22 Success Scenario: User selects a particular game. Next, user selects a particular date Next, user selects a particular time slot.

23 User selects Individual plan Selected plan will be reflected on dashboard

24 Alternative Scenario: a. Selecting a time slot that is already planned Result: Show a toast message that a plan is already made at that time b. Pressing cancel button Result: User will be redirected to home page without making any plan c. Select a past date Result: Warn user that past date cannot be chosen d. Select a past time

25 Result: Warn user that chosen time already passed 2.10 TEST CASE SCENARIO GROUP PLAN Description This test case describes how to test the process when an individual plans for a group. Preconditions The tester should have been logged in with a registered account for this app. He must have at least one friend in friend list. User clicks on Plan icon from menu bar. Post Conditions User will be able to select a particular game at a particular date and time. He will be able to invite selected friends to that event. He will also know how many are attending (Who accepted/rejected a plan). His plan will be reflected to dashboard. Database will update this new plan. Success Scenario: User selects a particular game, date and time just like test case of individual plan. Next user selects group plan option:

26 User can select friends from his current friends User clicks Group Invite button. That group plan will be added to dashboard with Type=MyGP:

27 Alternative Scenario: a. A friend invites to a group plan at that particular date and time, user already made a group plan Result: Notify owner of the plan that he cannot accept group plan from other users when he himself already made a group plan. b. No friend selected Result: Toast message will show that no friends were selected for that plan: c. Pressing cancel button Result: User will be redirected to home page without making any plan

28 2.11 TEST CASE SCENARIO USER DASHBOARD Description This test case describes how to test if the dashboard is working perfectly or not. Preconditions The tester should have been logged in with a registered account for this app. He should have been either made a plan or accepted plan from friends. Post Conditions Plans will be updated as a list on the Dashboard Database will update this new plan TEST CASE SCENARIO STATISTICAL CHART Description This test case describes how to test if the graphs are working correctly. Preconditions The tester should have been logged in with a registered account for this app. Database admin should have been provided data to database table. User clicks on charts icon from menu bar. Post Conditions User will be able to see data of selected game as chart on a screen. Success Scenario User selects a game from list of games and a chart type. Then he clicks on submit button:

29 A chart will be loaded on screen showing average data for days of a week. User can interact with chart by clicking on different parts Conclusion Testers are most welcome to execute new test cases and report to us for bugs.