Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

Test cases – Stirbu Mihai Gabriel

Step Description Expected Result Actual Result


1 Checking the functionality of By typing the link on PASS - The user was
the link the browser, the user able to use the link and
“file:///C:/Users/Mihai/Desk should gain access to connect to the “Login”
top/login-page/index.html” “Login” page. page.
using Mozilla Firefox latest
version.
2 Checking the visual element The visual element FAIL - The visual
“CODING – LOGO DESIGN” should be centred element is not centred,
above the “Login” the left and right
form. The image should distances are not
not contain any extra equal. The image
elements. contains a small
watermark “LOGO
DESIGN” which should
not be visible to the
user.
3 Checking the spelling of Every word should be FAIL- In the line
words and all extra spelled correctly, fonts containing “My App –
elements/misspellings/ should match every Login” the word
deviations from line. The “Copyright” “Login” is not BOLD
requirements presented on line at the bottom text to match “My
the “Login” page. should contain all the App”.
components usually The word “Usrname” is
presented. misspelled and it
should be “Username”
The word “Pasword” is
misspelled and it
should be “Password”.
The “Copyright” line is
missing the “Name of
the copyright owner”
and it is showing an
extra combination of
symbols and letters
that should not be
visible to the user –
“/p>”.
4 Check the presence of the The “Login” form FAIL – The “Show
usual options presented on a should have the Password”, “Forgot
“Login” form. following options Username/Password”,
presented: “Show “Don’t have an
Password”, “Forgot account? Sign up”
Username/Password”, options are missing.
“Don’t have an
account? Sign up”
5 Check if the inputted data in The user should be able PASS – After refreshing
the username field is still to refresh the page and the page, the username
present after refreshing the after hitting refresh, “atuny0” was still
page. the username should visible.
Credentials: be still visible.
"username": “atuny0”

6 Checking the maximum The username field FAIL – The username


capacity of the username should have a limited field does not have a
field. capacity for data input.limited capacity for
data input.
7 Checking the maximum The user should be able FAIL – The user is able
capacity of the password to type in maximum 9 to type in 10
field. characters. characters.
8 Checking the login The user should not be FAIL – The user was
functionality using a able to login with a able to login to the
password of 10 characters. password longer than 9 “Dashboard” page with
The credentials: characters. The user a 10 characters
"username": " dpettegre6" should not be able to password.
"password": "YVmhktgYVS" type in the whole The message:
password or the “Successfully logged
message “Invalid in!” with the “OK”
credentials!” should button that allows the
appear. user to access the
“Dashboard” page was
being displayed.
9 Checking the login The user should not be PASS – The user was
functionality with no able to access the not granted access to
credentials. “Dashboard” page the “Dashboard” page.
without inputting data The message:
in the username and {"message”: “Invalid
password fields. credentials"} was being
displayed.

10 Checking the login The user should not be PASS – The user was
functionality after inputting able to access the not granted access to
data just in the username “Dashboard” page. the “Dashboard” page.
field using a username from The message:
the database: {"message”: “Invalid
"username": "atuny0" credentials"} was being
displayed.

11 Checking the login The user should not be PASS – The user was
functionality after inputting able to access the not granted access to
data just in the password “Dashboard” page. the “Dashboard” page.
field using a password from The message:
the database: {"message”: “Invalid
"password": "9uQFF1Lh" credentials"} was being
displayed.

12 Checking the compliance to After failing to login, FAIL – The message


requirements of the message the user should receive being displayed is
being displayed after failing the message “Invalid {"message”: “Invalid
to login. credentials!” with a credentials"} which
Credentials: working animation of a contains extra symbols
"username": "ggude7" stop sign showing a red and words instead of
"password":"MWwlaeWcOo X. the “Invalid
F6" credentials!” message
but with the correct
animation showing the
red X.
13 Checking the compliance to The user should receive PASS - The user
requirements of the message the message received the correct
displayed after successfully “Successfully logged message “Successfully
logging in with the in!” and an “OK” logged in!” and the
credentials: button to press that working animation of a
"username": "yraigatt3" allows the user to green checkmark along
"password": "sRQxjPfdS" access the “Dashboard” with the “OK” button
page and a working that allows the user to
animation of a green access the “Dashboard”
checkmark. page.
14 Checking if you can The user should be able PASS – The user
successfully login with a to successfully login successfully logged in.
password <= 9 characters. and access the The message
The credentials used: “Dashboard” page with “Successfully logged
"username": "umcgourty9" a password <= 9 in!” was being
"password": "i0xzpX" characters. displayed with the
"username": "yraigatt3" “OK” button that allows
"password": "sRQxjPfdS" further access to the
“Dashboard” page.
15 Checking the login The user should be able FAIL – The user was not
functionality using to attempt to login able to attempt to login
credentials and ENTER key after typing the after typing the
The credentials: username, password, username, password
"username": "atuny0" then by pressing the and then by pressing
"password": "9uQFF1Lh" ENTER key. the ENTER key.
16 Checking the login The user should be able PASS – The user was
functionality using the to attempt to login able to attempt login
ENTER key after navigating after navigating the using ENTER key after
the fields with TAB key The fields using TAB key navigating with TAB
credentials used: and then hit ENTER key key.
"username": "atuny0" after reaching the The message:
"password": "9uQFF1Lh" “Login” button. “Successfully logged
in!” with the “OK”
button that allows the
user to access the
“Dashboard” page was
being displayed.

17 Checking the login The user should be able PASS – The user was
functionality using to attempt login by able to attempt login
credentials and CLICK on CLICKING the “Login” by CLICKING on the
“Login” button. button. “Login” button.
The credentials: The message:
"username": "atuny0" “Successfully logged
"password": "9uQFF1Lh" in!” with the “OK”
button that allows the
user to access the
“Dashboard” page was
being displayed.

18 Checking the further access The user should be able PASS – The user was
to the “Dashboard” page to access the able to access the
after using ENTER key on the “Dashboard” page after “Dashboard” page after
“OK” button. hitting the ENTER key hitting the ENTER key.
Credentials: when the message
"username": "umcgourty9" “Successfully logged
"password": "i0xzpX" in!” appears along with
the” OK” button.
19 Checking the further access The user should be able PASS – The user should
to the “Dashboard” page to access the be able to access the
after CLICKING on the “OK” “Dashboard” page after “Dashboard” page after
button. CLICKING on the” OK” CLICKING on the ”OK”
Credentials: button. button.
"username": "umcgourty9"
"password": "i0xzpX"

20 Checking what happens The user should be able FAIL - After clicking
when you receive the to access further the somewhere else on the
“Successfully logged in!” “Dashboard” page page, the “Dashboard”
message with the “OK” because he was was not loading,
button but the user clicks successfully logged in. instead the user is sent
somewhere else on the page back to the “Login”
but not on the “OK” button. page.
21 Checking the “Logout” The user should be able PASS - The user was
button of the “Dashboard” to use the “Logout” able to use the
page. button and return to “Logout” button and
the “Login” page. return to the “Login”
page.
22 Checking if the user can The user should be able PASS – The user was
successfully log in with a 9 to log in. able to log in.
characters password. The message:
Credentials: “Successfully logged
"username": "kdulyt" in!” with the “OK”
"password": "5t6q4KC7O" button that allows the
user to access the
“Dashboard” page was
being displayed.
23 Checking for the presence of The disabled user FAIL – The “Login” page
functions to login for should have options to has no option for the
disabled persons. input data, receive and disabled.
understand data from
the “Login” page like
voice control, text
adaptation, sound
activation.
25 Checking what happens after After successfully log in PASS - After
successfully log in and and instead of selecting successfully log in and
instead of selecting the “OK” the “OK” button, the instead of selecting the
button, the user hit refresh. user hit refresh, he “OK” button, the user
The credentials: should be returned on hit refresh, he is
"username": "atuny0" the “Login” page and returned on the
"password": "9uQFF1Lh" the username should “Login” page and the
be saved in the username is saved in
username field. the username field.
26 Checking what happens after After failing to log in PASS - After failing to
failing to log in and instead and instead of selecting log in and instead of
of selecting the “OK” button, the “OK” button, the selecting the “OK”
the user hit refresh. user hit refresh, he button, the user hit
The credentials: should be returned on refresh, he is returned
"username": "atuny0" the “Login” page and on the “Login” page
the username should and the username is
be saved in the saved in the username
username field. field.
27 Checking if the username The user should be FAIL – The user is able
and password fields accept warned whit a red pop- to use special
special characters. up message that he is characters in both
not allowed to input fields.
other type of data
beside letters and
numbers.
28 Check the access to the The user should not be FAIL – The user is able
“Dashboard” page after able to log in, hit the to access the
hitting “Go back” and “Go “Go back button”, then “Dashboard” page after
forward” buttons when hit the “Go forward” hitting “Go back” and
successfully log in. button and access the “Go forward” buttons
The credentials: “Dashboard” page. without typing in the
"username": "atuny0" After hitting the “Go password again.
"password": "9uQFF1Lh" back” button, the user
should be returned to
the “Login” page and
the password field
should be empty.
29 Check if the password field The user should be FAIL – After returning
remains completed after returned to the “Login” to the “Login” page,
accessing another page and page which presents username and
then hit “Go back” button and empty password password fields were
The credentials: field. still completed and the
"username": "atuny0" user is able to access
"password": "9uQFF1Lh" the “Dashboard” page
after returning from
another page with this
access order
30 Checking if the credentials The user should be able PASS - The user was
can be saved as “Saved to save the username able to save the
Logins” and password. username and
The credentials: password after
"username": "atuny0" successfully logging in.
"password": "9uQFF1Lh"

You might also like