TestCasesGroup1

1. Register Account
	• Sunny
		○ 3 users
	• Rainy
		a. Already Registered
		b. Invalid Email
		c. Non-matching Password
2. Forgot Password
	• Sunny
		○ 3 users
	• Rainy
		a. Email does not exist
		b. 2 users
3. Log In
	• Sunny
		a. 3 users
	• Rainy
		a. 3 non-valid
		b. Possibly missing info
4. Log Out
	• Sunny
		a. 3 users
	• Rainy
		a. Not logged in
		b. Straight to link
		c. ???
5. Comment
	• Sunny
		a. Comment on self
		b. Comment on other
		c. 2nd user
	• Rainy
		a. Need More Info on commenting
6. Reply
	• Sunny
		a. 3 users
	• Rainy
		a. Need more info
7. Request Family Link
	• Sunny
		a. 3 users
	• Rainy
		a. Straight to Link
		b. Request self
		c. ???
8. Request Admin Privileges
	• Sunny
		a. 3 users
	• Rainy
		a. Cancel
		b. Straight to link
9. Deny Admin Request (by Admin)
	• Sunny
		○ Deny Requests
	• Rainy Day
		○ Attempt no requests
		○ Straight to link
		○ Cancel
10. Accept Admin Request (by Admin)
	• Sunny
		○ Confirm requests
	• Rainy
		○ Attempt no requests
		○ Straight to link
		○ Cancel




1. Register Account
	ID: A&S-001R (Fig. 1)
	Name: Register User Success Participating Actors: User
	Entry Condition:
	- The user does not have an account, and wishes to use the application. - The user is in the main page “famillytree.com”
	Events flow:
		1. 1-  User clicks on the register button
		2. 2-  System redirects to and displays the registration page
		3. 3-  User enters the information required to create account:
a. Name
b. Email (will be user name) c. Password
d. Confirm Password
		4. 4-  System validates data
a. User name (email) is valid
b. User name (email) available
c. Password meets the required specifications d. Personal information valid
		5. 5-  Redirect to Welcome Page
	Exit Conditions:
	User is successfully registered
	Alternative flow: None
	Non-Functional Requirement:
	1- Registration process should take no longer than 1sec after submitting form. 2- Registration process should be a one-click process.
	ID: A&S-002R (Fig. 2)
	Name: Register User Incorrect Input Participating Actors: User
	Entry Condition:
	- The user does not have an account, and wishes to use the application. - The user is in the main page “famillytree.com”
	Events flow:
	1- User clicks on the register button
	2- System redirects to and displays the registration page 3- User enters the information required to create account:
	8
		1. Name
		2. Email (will be user name)
		3. Password
		4. Confirm Password
		5. 4-  System validates data
a. User name (email) is valid
b. User name (email) available
c. Password meets the required specifications d. Personal information valid
		6. 5-  System finds invalid entered data
	Exit Conditions:
	System highlights incorrect input and ask user to correct it
	Alternative flow: None
	Non-Functional Requirement:
	1- Data validation process should take no longer than 1sec
	2- Data validation should be robust, not crashing when invalid input is entered
	ID: A&S-003R (Fig. 3)
	Name: Register User Duplicate Email Participating Actors: User
	Entry Condition:
	- The user does not have an account, and wishes to use the application. - The user is in the main page “famillytree.com”
	Events flow:
		1. 1-  User clicks on the register button
		2. 2-  System redirects to and displays the registration page
		3. 3-  User enters the information required to create account:
a. Name
b. Email (will be user name) c. Password
d. Confirm Password
		4. 4-  System validates data
a. User name (email) is valid
b. User name (email) available
c. Password meets the required specifications d. Personal information valid
		5. 5-  System find email is already in use
	Exit Conditions:
	System shows error and ask user to enter a new email.
	9
	Alternative flow: None
	Non-Functional Requirement:
	1- Validation should not take more than 1sec.
	2- System should be robust, not crashing when duplicate email is entered.
	ID: A&S-004R (Fig. 4)
	Name: Register User Weak Password Participating Actors: User
	Entry Condition:
	- The user does not have an account, and wishes to use the application. - The user is in the main page “famillytree.com”
	Events flow:
		1. 1-  User clicks on the register button
		2. 2-  System redirects to and displays the registration page
		3. 3-  User enters the information required to create account:
a. Name
b. Email (will be user name) c. Password
d. Confirm Password
		4. 4-  System validates data
a. User name (email) is valid
b. User name (email) available
c. Password meets the required specifications d. Personal information valid
		5. 5-  System finds that password is too weak
	Exit Conditions:
	System shows error and ask user to enter a stronger password
	Alternative flow: None
	Non-Functional Requirement:
	1- Password verification should not take longer than 1 sec 2- Password requirements should be easy to understand

2. Forgot Password

3. Log In
	ID: A&S-001L (Fig. 9)
	Name: Login Success Participating Actors: User
	Entry Condition:
	- The user is in the main page “famillytree.com” - The user is already registered
	Events flow:
	1. User enters the log in information
	2. System check credential and grant access 3. System presents Welcome Page
	Exit Conditions:
	User is logged in the system
	Alternative flow: None
	Non-Functional Requirements:
	1- Log in process should take no longer than 0.5 sec 2- Password should not be shown while the user types
	ID: A&S-002L (Fig. 10)
	Name: Login without Password Participating Actors: User
	Entry Condition:
	- The user is in the main page “famillytree.com” - The user is already registered
	Events flow:
	1. User enters the log in information 2. User leaves password area blank 3. User clicks Login
	Exit Conditions:
	System shows error: “Incorrect Username and/or Password”
	Alternative flow: None
	Non-Functional Requirements:
	1- Log in process should take no longer than 0.5 sec 2- Error message should be easy to understand
	13
	ID: A&S-003L (Fig. 11)
	Name: Login wrong Password Participating Actors: User
	Entry Condition:
	- The user is in the main page “famillytree.com” - User is on third attempt to login
	- The user is already registered
	Events flow:
	1. User enters the log in information 2. User inputs wrong password
	3. User clicks Login
	Exit Conditions:
	System presents message: “Do you want to reset your password?” System highlights link that reads “Forgot Password”
	Alternative flow: None
	Non-Functional Requirements:
	1- Reset password process should be user friendly
	2- “Forgot Password” link should be easy to find and accessible
	ID: A&S-004L (Fig. 12)
	Name: Username Not Found Participating Actors: User
	Entry Condition:
	- The user is in the main page “famillytree.com” - The user is already registered
	Events flow:
	User enters the log in information
	1. User enters wrong username 2. User enters password
	3. User clicks Login
	Exit Conditions:
	System shows error: “Incorrect Username and/or Password”
	Alternative flow: None
	Non-Functional Requirements:
	1- Log in process should take no longer than 0.5 sec
	14
	2- System should be responsive 99% of the time
	ID: A&S-005L
	Name: Logout Participating Actors: User
	Entry Condition:
	- The user is login in the system - The user is already registered
	Events flow:
	1. User clicks on the logout link
	2. System present logout page which is the welcome page
	Exit Conditions:
	User is logout from the system
	Non-Functional Requirement:
	1- Logout process should not take longer than 0.5 sec 2- Logout should be a one-click process

4. Log Out
5. Comment
	ID: A&S-001SC (Fig. 25)
	Name: Share thought Participating Actors: User
	Entry Condition:
	- The user is in the welcome page - The user is already logged in
	Events flow:
	1- User clicks on the “Share Thought” button
	20
		1. 2-  System shows the text area, Submit and Cancel buttons
		2. 3-  The user writes on the text area an click submit
		3. 4-  Systems process the request
	Exit Conditions:
	System sends a request to the Family Tree Features System to update the page content.
	Alternative flow:
	3- User clicks Cancel
	a. System hides the text area
	Non-Functional Requirements:
	1- Sharing thought should be a one-click process
	2- System should process the request in less than 1 sec
	ID: A&S-002SC (Fig. 26)
	Name: Comment on own Thought Participating Actors: User
	Entry Condition:
	- The user is in the welcome page - The user is already logged in
	Events flow:
		1. 1-  User clicks on the “Comment” button
		2. 2-  System shows the text area, Submit and Cancel buttons
		3. 3-  The user writes on the text area an click submit
		4. 4-  Systems process the request
	Exit Conditions:
	System sends a request to the Family Tree Features System to update the page content.
	Alternative flow:
	3- User clicks Cancel
	a. System hides the text area, Submit and Cancel buttons
	Non-Functional Requirements:
	1- Sharing thought should be a one-click process
	2- System should process the request in less than 1 sec
	ID: A&S-003SC (Fig. 27)
	Name: Comment on Thought Participating Actors: User
	21
	Entry Condition:
	- The user is in the other user Welcome page - The user is already logged in
	Events flow:
		1. 1-  User clicks on the “Comment” button
		2. 2-  System shows the text area, Submit and Cancel buttons
		3. 3-  The user writes on the text area an click submit
		4. 4-  Systems process the request
	Exit Conditions:
	System sends a request to the Family Tree Features System to update the page content.
	Alternative flow:
	3- User clicks Cancel
	a. System hides the text area, Submit and Cancel buttons
	Non-Functional Requirements:
	1- Sharing thought should be a one-click process
	2- System should process the request in less than 1 sec

6. Reply
7. Request Family Link
8. Request Admin Privileges
	ID: A&S-002A (Fig. 18)
	Name: Request Right Participating Actors: User
	Entry Condition:
	- The user is in the welcome page - The user is already logged in
	Events flow:
	1- User click on the Request Admin Rights button 2- The system send a request to the Super Admin 3- System sends email to Super Admin
	Exit Conditions:
	System sends admin request to Super Admin
	Alternative flow: None
	17
	Non-Functional Requirement:
	1- Flagging Admin should be a one-click process 2- Process should take no longer than 1sec

9. Deny Admin Request (by Admin)
	ID: A&S-004A (Fig. 20)
	Name: Deny Rights
	Participating Actors: Super Admin
	Entry Condition:
	- The Super Admin is in the welcome page - The Super Admin is already logged in
	Events flow:
		1. 1-  Super Admin click on Admin Requests button
		2. 2-  The system shows a modal with al pending Admin Request
		3. 3-  Super Admin denies the request
		4. 4-  System sends email to requesting user
	Exit Conditions:
	System does not grant admin rights to requesting user
	18
	Alternative flow: None
	Non-Functional Requirement:
	1- Process should take no longer than 1sec 2- This should be user-friendly

10. Approve Admin Request (by Admin)
	ID: A&S-003A (Fig. 19)
	Name: Approve Rights Participating Actors: Super Admin
	Entry Condition:
	- The Super Admin is in the welcome page - The Super Admin is already logged in
	Events flow:
		1. 1-  Super Admin click on Admin Requests
		2. 2-  The system shows a modal with al pending Admin Request
		3. 3-  Super Admin approves the request
		4. 4-  System sends email to requesting user
	Exit Conditions:
	System grants admin rights to requesting user
	Alternative flow: None
	Non-Functional Requirement:
	1- Process should take no longer than 1sec 2- This should be user-friendly
11. Make Admin (by Admin)
	ID: A&S-001A (Fig. 17)
	Name: Admin Rights
	Participating Actors: Super Admin, Email Client
	Entry Condition:
	- The Super Admin is in the welcome page - The Super Admin is already logged in
	Events flow:
	1. Super Admin clicks Make Admin button
	2. System redirects to pop-up window
	3. System displays family member with no admin rights 4. Super Admin selects the users “Jorge” and “Linnet” 5. Super Admin click Submit
	6. System sends email to selected users
	Exit Conditions:
	Selected users are granted admin rights
	Alternative flow: None
	Non-Functional Requirement:
	1- Flagging Admin should be user-friendly 2- Process should take no longer than 1sec