#SL Module Feature Test Case

User Registration Verifying whether Registration

1 Management page appears

2 Grammatical or spelling mistake

on registration page
3 Clicking "create button" keeping
all the fields blank
4 Name field with empty input

Name field with preceding space

5 inputs

Name field with only special

6 characters(without alphabets)

7 Name field with only

numbers(without alphabets)
8 Name field with valid inputs

9 Email field with empty input

10 Email field with invalid format

11 Email field with numbers

12 Email field with only alphabets

13 Email field with valid format

14 Email field with already existed

mail id
15 Phone field with empty input

16 Phone field with alphabets

17 Phone field with special

characters
18 Phone field with alpha-numeric
input
19 Phone number field with invalid
country code
20 Phone number field with 10 digits

21 Phone number field with 12 digits

22 Phone number field with space in

between valid input
23 Phone number field with valid 11
digits
24 Phone field with already existed
phone number
25 Clicking country code dropdown
button
26 Password field empty

27 Password field with alphabets

28 Password field with special

characters
29 Password field with numbers

30 Password field with lower and

upper case alphabets
31 Password field with space inputs

32 Verifying password field is

masked
33 Clicking pick icon on password
field
34 Password field with wrong length
input
35 Password field with minimum
input lentgh (8)
36 Password field with easy guesing
input
37 "I agree…." Checkbox clicking for
checked
38 "I agree…." Checkbox clicking for
unchecked
39 Clicking "Terms of use" hyperlink

40 Clicking "Privacy Policy" hyperlink

41 Clicking reCAPCHA checkbox

42 Clicking "Login Now" hyperlink on

sign up form
43 Filling all the fields with valid
inputs
44 Verification Code field with
alphabets
45 Verification Code field with
special characters
46 Verification Code field with alpha-
numeric input
47 Verification Code field with only
space
48 Verification Code field with empty
input
49 Verification Code field with less
than min length pin
50 Verification Code field with more
than max length pin
51 Verification Code field with
expired pin no
52 clicking "RESEND" hyperlink on
verification page
53 Correct code on verification code
field
54 phone no registration without
submitting verification code
55 Clicking "Facebook" API for sign
up
56 Clicking "Google" API for sign up

57 Sign In Verifying whether Sign In page

appears
58 Grammatical or spelling mistake
on Sign In page
59 Clicking "Facebook" API for Sign In

60 Clicking "Google" API for Sign In

61 Clicking Sign In button keeping all
field blank
62 Empty Email or phone and valid
password
63 Valid email or phone and empty
password
64 Invalid email and valid password

65 Invalid phone no and valid

password
66 valid email and invalid password

67 valid phone no and invalid

password
68 valid phone no and valid
password
69 valid email and valid password

70 Checking password field is

masked
71 Clicking Eye icon on password
field
72 Checking "Forgot password"
hyperlink
73 Remember me chechbox
checkable or not
74 Remember me functionality
works when checked
75 Clicking "Sign Up Now" hyperlink
 Expected Result Actual Result Test Data

A registration UI should apear As expected

No grammatical or spelling mistake As expected

Proper error message should appear on every As expected

field
Should give a error message under name field. As expected

It should not take preceding space inputs It takes preceding space inputs Nafis

Should not take special characters without It takes special characters without #$@!
alphabets alphabets

Should not take numbers without alphabets It takes numbers without alphabets 12345

Should accept the input As expected Nafis

An error message should appear under email As expected

field
An error message should appear under email As expected abc@a.99
field
An error message should appear under email As expected 12345
field
An error message should appear under email As expected abc
field
Should accept the email format As expected sqa@yopmail.com

An error message should appear under email As expected abc@gmail.com

field
An error message should appear under phone As expected
field
An error message should appear under phone As expected abcd
field
An error message should appear under phone As expected !@#$%
field
An error message should appear under phone As expected 1234as
field
An error message should appear under phone As expected 12345678912
field
An error message should appear under phone As expected 0167416339
field
An error message should appear under phone As expected 016741633981
field
An error message should appear under phone As expected 01674163 983
field
Should accept the number As expected 01674163398

An error message should appear telling already As expected 01948301376

existed number
Should show the list of country code available As expected

An error message should appear under As expected

password field
IT should accept As expected qwertyui

IT should accept As expected !@#$%^&*

IT should accept As expected 987654321

IT should accept As expected abcdEFGH

IT should accept As expected

Written password should be masked As expected qwertyui

Written password should be visible As expected qwertyui

An error message should appear telling As expected abcdefg

minimum length of password
Password should be accepted As expected a1b2c3ed4

An error message should appear telling too easy As expected abcdefgh / 123456
password
It should be checked As expected N/A

It should be unchecked As expected N/A

It should relocate to a page named "Terms of As expected N/A
use"
It should relocate to a page named "Privacy As expected N/A
Policy"
The checkbox should be checked As expected N/A

Should lead to Sign In form As expected N/A

Locate to verification page asking for OTP pin As expected N/A

sent in phone number
Should appear a error message As expected abcde

Should appear a error message As expected !@#$%^&

Should appear a error message As expected abc123

Should appear a error message As expected N/A

Should appear a error message As expected N/A

Should appear a error message As expected 12345

Should appear a error message As expected 1234567

Should appear a error message As expected Sent OPT pin

Should send another pin on the given number As expected N/A

Should Register and lead to Sign In page As expected Sent OTP pin

Should not register phone no without submitting As expected 01674163398

phone no
Should locagte to a FB sign in page if FB ID is As expected N/A
signed out before.
Should locagte to a google sign in page if google As expected N/A
ID is signed out before.
A Sign In UI should apear As expected N/A

No grammatical or spelling mistake As expected N/A

Should locagte to a FB sign in page if FB ID is As expected N/A

signed out before.
Should locagte to a google sign in page if google As expected N/A
ID is signed out before.
Should appear error message under relavent As expected N/A
fields
Should appear an error message As expected pass: 987654321

Should appear an error message As expected Email:

shahriar@yopmai
l.com
Should appear an error message As expected email: 1234abcd
pass: 987654321
Should appear an error message As expected phone: 12345678912
pass: 987654321
Should appear an error message As expected email: shahriar@yopmail.com
pass: qwertyui
Should appear an error message As expected phone:
01746086439
Should appear the home page As expected phone:
01746086439
Should appear the home page As expected email: shahriar@yopmail.com
pass: 987654321
Written password should be masked As expected Pass:qwertyui

Written password should be visible As expected Pass:qwertyui

should lead to a recovery code page As expected N/A

Checkbox should be checked or unchecked As expected N/A

depending on the previous state
Home page should appear As expected N/A

Sign up UI should appear As expected N/A

 TEST CASE
PASS 72
FAIL 3
Not Executed 0
Out of Scope 0
TOTAL 75
Test Steps Bug Screenshots Status Remarks

1. Go to url
"www.rokomari Passed
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url
"www.rokomari NameInavlid_space Failed
.com"

1. Go to url
"www.rokomari NameInvalid_specialCharFailed
.com"

1. Go to url NameInvalid_numbers Failed

"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
1. Go to url Passed
"www.rokomari
.com"
 Test Case Report
Project Name - Rokomari.com
Module Name - User Management
Test Case Version -
Written By Fahad
Executed By Fahad
Reviewed By -

TEST EXECUTION REPORT

Test Case PASS FAIL Not Executed Out Of Scope Total TC

72 3 0 0 75

Grand Total 72 3 0 0 75

LIMITATIONS
Documents Received Useful
PRD No No
USER STORY No No

Testing Type
Description
in Scope

Yes/ No.
Justification (If No):
This type of testing ignores the internal parts and focuses only
Functional Testing
on the output to check if it is as per the requirement or not.

Yes/ No.
Justification (If No):
Testing of all integrated modules to verify the combined
Integration Testing
functionality after integration is termed as Integration Testing.
 Integration Testing
functionality after integration is termed as Integration Testing.

Yes/ No.
Justification (If No):
Testing having the mindset of “attitude to break” using incorrect
Negative Testing
data and invalid inputs.

Yes/ No.
Justification (If No):
Usability Testing Test application from user friendliness perspective.

Yes/ No. Browser Compatibility Testing is performed for web applications

Justification (If No): and it ensures that the software can run with the combination of
Browser Compatibility
different browser and operating system. This type of testing also
Testing
validates whether web application runs on all versions of all
browsers or not.
Yes/ No.
Justification (If No):
Boundary Value There is an upper and lower boundary for each range and
Testing testing is performed on these boundary values.

Yes/ No.
Justification (If No): Risk-Based Testing includes testing of highly critical
functionality, which has the highest impact on business and in
Risk Based Testing
which the probability of failure is very high.
Or
Regression Testing
Testing an application as a whole for the modification in any
module or functionality is termed as Regression Testing.
Total No. Status Result :
72 PASS
3 FAIL
0 Not Executed New Features Testing Scope Testing Environment :
0 Out of Scope Test Environment

Test Case Report

4%

96%

PASS FAIL Not Executed Out of Scope

Google Chrome Browser