Page Comparison

Beza is a senior official in Ministry of Ag in Ethiopia and wants to sign up in quick efficient way

Happy Flow

•  Beza Click on SIGNUP
•  Beza entered Valid First Name, Valid Last Name, Valid Email Address, Valid User Name, Valid Phone Number and click NEXT STEP
•  Beza entered OTP and Click on NEXT STEP
•  Beza entered Valid password and Same password entered in confirm password filed, Click on Next Step

Step 11-

Recommendations from QA

•  First Name field should

• be

• mandatory field with red *

2 - First Name should not include special Characters and Numeric

3 - Beza enter invalid First name (includes special character's and Numeric) and click on NEXT STEP button, application should throw Error message saying “Enter Valid First Name”

• . If we agree to have this as mandatory, we should have the following checks:

a. Without entering First Name in FIRST NAME filed and Beza try to click on NEXT STEP button, NEXT STEP button should be in read only

5 - b. Without entering First Name and Beza try to click on NEXT STEP button, FIRST NAME field (the box) should heightened with red colour indicating Beza to enter FIRST NAME - optional

6 - c. Beza didn't enter FIRST NAME and click on NEXT STEP button , application should throw validation message saying “Enter First Name”

7 - d. Beza enter invalid First Name (includes special character's and Numeric) and click on NEXT STEP button, application should throw Error message saying “Enter Valid Last Name”

•  Last Name field should

• be optional and not mandatory. That is no red *, but if we decide to have ti mandatory, we should have the following tests:

a. LAST NAME should not include special Characters and Numeric - Optional

9 - b. Beza enter invalid Last Name (includes special character's and Numeric) and click on NEXT STEP button, application should throw Error message saying “Enter Valid Last Name” - Optional

10 - c. Without entering LAST NAME in LAST NAME field and Beza try to click on NEXT STEP button, NEXT STEP button should be in read only - Optional

11 - d. Without entering LAST NAME and Beza try to click on NEXT STEP button, LAST NAME field (the box) should heightened with red colour indicating Beza to enter LAST NAME - Optional

12 - e. Beza didn't enter LAST NAME and click on NEXT STEP button , application should throw validation message saying “Enter LAST Name” - optional 13 -

•  When entering phone/ mobile number, there should be a dropdown list to select country with flag and code which needs to be selected - mandatory

a. Beza didn't select country with flag and country code in drop down list , application should throw validation message saying “ Select Country code”

b. Beza select wrong country flag, country code in drop down list and entered valid phone/mobile numbers. Application should throw error message saying “Select valid Country Code “

c. Beza select correct country flag, country code in drop down list and entered invalid phone/mobile numbers. Application should throw error message saying “Enter valid Phone/Mobile number“

d. Beza select wrong correct country flag, country code in drop down list and entered invalid phone/mobile numbers. Application should throw error message saying “Select valid Country Code “ and “Enter valid Phone/Mobile number“

Error messages

•   Beza should enter valid email address with proper Domain name example (

• Beza@hotmail.com)

14 - a. Beza enters Invalid Email, application should throw Error message in red colour saying “Enter Valid Email Address” next to /below/above You’ll receive an OTP on your email15 -

•  USERNAME should not include special character's in USERNAME field (can have numeric)

a. Beza enters invalid username $Beza or beza$ and it should show an error below the field

•  USERNAME if not available should be suggested

a. Beza as a username is already taken, the system should show the message that username doesn’t exist and suggest two different available usernames, for example, Beza01 and Beza02 are available

Validation messages

•  Without entering Email Address in EMAIL ADDRESS field and Beza try to click on NEXT STEP button, Application should throw validation message saying “Enter Valid Email Address”

•  Without entering Email Address in EMAIL ADDRESS field and Beza try to click on NEXT STEP button, NEXT STEP button should be in read only

17 - USERNAME should not include special character's in USERNAME filed

•   Beza didn't enter USERNAME and try to click on NEXT STEP button , application should throw validation message saying “Enter UserName”

•  Without entering UserName in USERNAME field and Beza try to click on NEXT STEP button, NEXT STEP button should be in read only

20 - Beza should enter Phone Number with Country Code

•   Beza didn't enter PHONE NUMBER and try to click on NEXT STEP button , application should throw validation message saying “Enter PHONE NUMBER”

•  Without entering Phone number in PHONE NUMBER field and Beza try to click on NEXT STEP button, NEXT STEP button should be in read only

23 - Beza entered invalid phone number, Application should throw validation message saying “Enter Valid Phone Number“

NOTE : 1 - Usually some users don't have last name

2 - Open questions :

•  For phone number how many numbers can be enter in Phone number field

3 - Phone number should include county code or treat it as Mobile number ?Step 2 1 -

Recommendations from QA

•  Application should send valid code in the form of numeric

2 - User can’t use the same code twice for Sign up

•  RESEND button should be active only if the time is elapsed (120 seconds) for entering OTP and there should be a message and question mark for tool tip
•   Beza click on RESEND, Application should display Validation message saying “CODE sent successfully”
•  If two or more OTPs get delivered, the most recent should be valid for sign up - optional (to be discussed)

Validation messages

•  Without entering code and

• try to click on NEXT STEP button, NEXT STEP button should be in read only

•   Beza didn't enter code and try to click on NEXT STEP button , application should throw validation message saying “Enter Code”

5 - Error messages

•   Beza enter Invalid code and try to click on NEXT STEP button , application should throw

• Error message saying “Enter Valid Code”

•   Beza

• accidentally try to enter alphabets, Application should not allow to enter

7 - When Beza received first code through email, but accidently click on resend application should allow recent code to validate

8 - Beza click on RESEND, Application should display Validation message saying “CODE sent successfully”

Step 3

1 - Password Open questions:

•  Should there be expiry of this step. For example, user left in between without entering OTP or didn’t get OTP but didn’t close the application. He comes next day, will he be able to RESEND OTP.

Step 3

•  Password should contains at least 8 character's which includes Alphabets, 1 Numeric , 1 special character

a. If password is less than 8 characters application should display validation message saying “Password should contains at least 8 character's which includes Alphabets, 1 Numeric, 1 special Character 2 - Character“ in Enter Password field

•   Beza enter invalid Password in Enter Password field , Application should throw Error message saying “Enter valid password”

•   Beza didn't enter Password in Enter Password field, Application should throw Validation message saying “Enter password”

•  Application should not allow Beza to enter password in Confirm Password field first without entering in Enter password field

•   Beza enter wrong password in Confirm password field, application should throw error message saying

6 - If password is less than 8 characters application should display validation message saying “Password should contains at least 8 character's which includes Alphabets, 1 Numeric, 1 special Character“ in Enter Password field

• “Passwords do not match“
•  After Beza enters Valid password in Enter Password field and Confirm password field, application should enable Next Step

•  After Beza enters invalid password in Enter Password field and Confirm password field, application should not enable Next Step

•   Beza

• clicks on eye symbol in Enter Password field and she need to hold to view the password, after unclick password should hide

•   Beza

• clicks on eye symbol in Confirm Password field and she need to hold to view the password after unclick password should hide

•  Application should show green colour tick mark next to Enter Password filed to make sure that user enter valid password

•  Application should show green colour tick mark next to Confirm Password filed to make sure that user enter valid password

•  Application should show X in red colour next to Enter Password filed to make sure that user enter invalid password/wrong password

•  Application should show X in red colour next to Confirm Password filed to make sure that user enter invalid password/wrong password

•   Beza enter Password in Enter Password field and didn't enter password in Confirm password filed, application should not enable NEXT STEP unless it is in read only mode

•   Beza enters valid password in Enter password field application should display green tick, but Beza enters wrong password in confirm password field application should display X symbol in red colour

Notes : what is the maximum password strength?

Matt is a senior program manager in a specific food value chain and wants to sign up using google

• right not only google sing on

Matt forgot his password and wants to recover in simple way

• email based link with OTP

• no secret questions or other security for the time being

Guided step by step way to help user customise the settings and show around using tooltips

• Customise - logo, color and adding data policies

• Quick guided tour of the tabs starting with adding team members

Guided step by step way to help user customise the settings and show around using tooltips

• Quick guided tour starting with adding participants

Important tip (skippable)

• Random tips

Dashboard tab that gives quick view of the participants as well as quick button to add or update participants

• Adding participants in three steps process

• Individual participants activity is low priority as of now

A tab for quick view of the network level activity

Dashboard to give quick overview of whose subscription is about to end and any associated tickets

User wants to change attributes related to own profile and add team members or guest viewers