Professional Documents
Culture Documents
Test Cases Azimut Vision Website - SMG
Test Cases Azimut Vision Website - SMG
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.
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"