Search Scenarios

1. Search results displayed should be relevant to search keyword

2. % sign in search keyword should not redirect to 404 ERROR

3. Application should not crash if user inserted % in search field

4. When user start typing word in text box it should suggest words
that matches typed keyword
5. There should be pre-defined search criteria for auto complete e.g.
after typing first 3 letter it should suggest matching keyword
6. When user clicks on any link from result and navigates back, then
result should be maintained

7. After clicking Search field - search history should be displayed

(latest search keyword)
8. All search keyword/filters should get cleared on clicking Reset
button

9. Search results should be cleared on clicking clear search button

10. History displayed in search field should be relevant to logged in

user only
11. Pagination should be tested for searches returning high number of
records
12. Total number of search records/results should be displayed on
page
13. Search keyword should get highlighted with color in the search
results
14. For ecommerce sites - search keyword should suggest similar kind
of product/items

15. For Advanced Search - limited search filters should be provided

16. Water text should be provided for user to understand what to
search
17. Validate search rules defined for “Exact Match” with the search
key word
18. Validate search rules defined for “Similar Match” with the search
key word
19. Validate search rules defined to search with a set of keywords
20. User should be able to search when he enters the keyword and
hits ‘Enter’ button on keyboard
 Placement & UI of Search Bar

– Website Search Bar location is very essential. Usually it is in the Header section on top
right portion of the screen.

– Look & Feel and Size of the Search Box. Is it attractive and engaging enough to make
you perform a search instead of roaming on website pages?
– Is Placeholder text(displayed within the search box and disappear when you start
typing) is enabled?

– Is font family used in search keyword matching overall theme and layout?

Is Site Search Suggestions Enabled?

– Is your website search having auto suggest feature?

– How smoothly it populates the list of suggestions as you starts typing into the search
box?

– Are the suggestions properly updated when you enter / remove a keyword?

– Are the suggested results relevant to the keyword you are typing?

– What happens when you click on any suggestion? Is it redirecting to proper result page?

Advance Search Feature

– Is your website having Advance Search feature?

– How can you access advance search window? Is it feasible and user friendly?

– What are the options and extra features it provides? Are all the features working
properly and producing appropriate search results?

– Combination of different search criteria must produce proper results. Same applied for
individual selection.
– Searching through Advance features should not populate 0 Result. If there is a case, that
particular criteria should be hidden.
Search Results

– What happens when you click Search button without entering any keyword?

– Does the search box keeps the history of previously searched keywords?

– Are you getting the proper result for what you have searched?

– Do the result page title contains searched keyword?

– How many search results are displayed per page? Is pagination enabled when you have
more results per page?

– In which order the search result is organized? Can you change the order?

– Is there a facility to search again from result page itself?

– There must not be any discrepancy in result when searching with same keyword
multiple times.

– How good is the performance of rendering results for most frequently used search
keywords?
– What happens when you search with a keyword that does not produce any result? There
must be a page showing you proper message with a box to search again.
– How feasible it is for user to navigate back to same search result page after clicking on
any result link?
Responsive is Must

– Are you able to see each and every feature of Search in responsive mode?

– How user friendly is Search in Mobile devices? It must not be frustrating.

– Is Advance search working properly in responsive mode?

– All the images and visuals in Search result should be properly displayed in responsive
screen.
 Test Cases of Google Search

1. Verify that the response fetched for a particular keyword

is correct and related to the keyword, containing links to
the particular webpage

2. Verify that the response are sorted by relevancy in

descending order i.e. most relevant result for the keyword
are displayed on top
3. Verify that response for multi word keyword is correct

4. Verify that response for keywords containing

alphanumeric and special characters is correct
5. Verify that the link title, URL and description have the
keyword highlighted in the response
6. Verify auto-suggestion in Google e.g. providing input as
'fac' should give suggestions like 'facebook', 'facebook
massenger', 'facebook chat' etc
7. Verify that response fetched on selecting the suggested
keyword and on providing the keyword directly should be
same
8. Verify that the suggestion provided by Google are sorted
by most popular/relevant suggestions
9. Verify that user can make search corresponding to
different categories - web, images, videos, news, books etc
and response should correspond to the keyword in that
category
10. Verifyonly
that misspelled keyword should get corrected
and response corresponding to the correct keyword should
get
11. displayed
Verify that multi word misspelled keywords also get
corrected
12. Verify the performance of search- check if the time
taken to fetch the response is within the ballpark
13. Verify that total number of results fetched for a
keyword
14. Verify that the search response should be localised that
is response should be more relevant to the country/area
from which the search request is initiated
15. Verify Google calculator service- make any arithmetic
request, calculator should get displayed with correct result
16. Verify Google converter service- make request like-
10USD in INR and check if the result is correct
17. Verify search response for a large but valid strings
18. Verify that incorrect keywords - keywords not having
related result should lead to "did not match any
documents" response
19. Verify that user can make search using different
languages
20. Verify that for a keywords, some related search terms
are also displayed to aid user's search
21. Verify that for number of results more than the limit on
a single page, pagination should be present, clicking on
which user can navigate to subsequent page's result
22. Verify Google's advanced search options like- searching
within a website, searching for files of specific extension

23. Verify if the search is case-insensitive or not

24. Verify the functionality of "I'm feeling Lucky" search-

the top most search result should get directly returned (but
as of now google doodle page link is displayed)

Front End - UI Test Cases of Google Search

1. Verify that Google Logo is present and centre aligned

2. Verify that the search textbox is centre aligned and
editable
3. Verify that search request should get hit by clicking on
search button or hitting enter after writing the search term
4. Verify that in the search result- webpage's title, URL and
description are present
5. Verify that clicking the search result will lead to the
corresponding web page
6. Verify that pagination is present in case number of
results are greater than the maximum results allowed in a
page
7. Verify that user can navigate to a page number directly
or move to previous or next page using the links present

8. Verify that different languages links are present and gets

applied on clicking the same

9. Verify that the total number of results for the keyword is

displayed

10. Verify that the time taken to fetch the result is

displayed
Test Cases for Search Functionality

Every web application by default will contain search

feature in it. Many search engines main functionality is
search feature. The parameters to be considered while
developing this feature or testing this feature are not
limited. There are many factors which should be looked
in when checking the coverage and usability of the
search text box in the application.

Preparation before testing the search functionality

1. Note down the valid input details for the search
feature.

2. Find out the minimum and maximum range.

3. Find out the depth of the search – document search,

word in a document, image search

4. Should document search display the size of the

document also? Similarly for image?

5. Any advanced search features like document or

image type selection to refine the search are available?

6. General set of input which can be given are

a. A-Z

b. a-z

c. 0-9

d. { [ ( ~ ! @ # $ % ^ & * ` | \ : ” ; ’ < > ? , . / * - + ) ] }

e. Blank spaces

Work with these inputs when testing the search

functionality

1. Special set of data which can be tried as input are

a. 2 blank spaces – These should be trimmed and error
message should be displayed
b. Blank spaces followed with special characters or
numbers
c. Special set like a* should give the results for all
characters starting with a.
d. Enter any sql query like “Select * from hello;” without
quotes and with quotes.

e. Search for tags.

f. Search for hyperlinks should be performed.

2. Search for documents. For advanced search feature,
search with different valid and invalid types of
documents. Document size should also be looked at.

3. Search for images with their sizes, names and types.

4. Any input data entered should return proper error

message guiding to enter the correct input.

5. Text in different panels of the page should be

searched. For example if left panel of the web page
contains menus and hyperlinks. Hyperlinks in that area
should be searched properly. If menus are also in scope
then they should also appear in the search results.

6. Search response time should be checked.

7. Try pressing “Enter” key instead of clicking “Search”
button.
8. Try searching in the page where a part of the page
has form with Submit button.
Search results testing
DO not ignore the search results just because you got
the results.
1. Check number of results in each page.
2. Check the count of the search results displayed in the
page.
3. Check if the search results are displayed by
popularity or most viewed or any other criteria
mentioned in the requirements.
4. Proper messages should be displayed when there
are no results.

5. Each search result should contain one link and few

lines containing the searched keyword. Link should
navigate to the page where the keyword exists.

6. Searched keyword should be highlighted in the

search results page and also in the page where the
keyword exists.
7. Pagination of the search results should be tested.
8. Number of search results display and the count
should also be tested.
Test Scenarios for Result Grid

1. Page loading symbol should be displayed when it’s

taking more than default time to load the result page

2. Check if all search parameters are used to fetch data

shown on result grid
3. Total number of results should be displayed on result
grid
4. Search criteria used for searching should be
displayed on result grid
5. Result grid values should be sorted by default
column.
6. Sorted columns should be displayed with sorting icon
7. Result grids should include all specified columns with
correct values
8. Ascending and descending sorting functionality
should work for columns supported with data sorting
9. Result grids should be displayed with proper column
and row spacing
10. Pagination should be enabled when there are more
results than the default result count per page
11. Check for Next, Previous, First and Last page
pagination functionality
12. Duplicate records should not be displayed in result
grid
13. Check if all columns are visible and horizontal scroll
bar is enabled if necessary
14. Check data for dynamic columns (columns whose
values are calculated dynamically based on the other
column values)
15. For result grids showing reports check ‘Totals’ row
and verify total for every column
16. For result grids showing reports check ‘Totals’ row
data when pagination is enabled and user navigates to
next page
17. Check if proper symbols are used for displaying
column values e.g. % symbol should be displayed for
percentage calculation
18. Check result grid data if date range is enabled
 Test Cases for Search Functionality

Test Cases for Search Functionality

Every web application by default will contain search feature in it.

Many search engines main functionality is search feature. The
parameters to be considered while developing this feature or testing
this feature are not limited. There are many factors which should be
looked in when checking the coverage and usability of the search
text box in the application.

Preparation before testing the search functionality

1. Note down the valid input details for the search feature.

2. Find out the minimum and maximum range.

3. Find out the depth of the search – document search, word in a

document, image search

4. Should document search display the size of the document also?

Similarly for image?
5. Any advanced search features like document or image type
selection to refine the search are available?

6. General set of input which can be given are

a. A-Z

b. a-z

c. 0-9

d. { [ ( ~ ! @ # $ % ^ & * ` | \ : ” ; ’ < > ? , . / * - + ) ] }

e. Blank spaces

Work with these inputs when testing the search functionality

1. Special set of data which can be tried as input are

a. 2 blank spaces – These should be trimmed and error message

should be displayed
b. Blank spaces followed with special characters or numbers

c. Special set like a* should give the results for all characters
starting with a.

d. Enter any sql query like “Select * from hello;” without quotes and
with quotes.

e. Search for tags.

f. Search for hyperlinks should be performed.

2. Search for documents. For advanced search feature, search with

different valid and invalid types of documents. Document size should
also be looked at.
3. Search for images with their sizes, names and types.

4. Any input data entered should return proper error message

guiding to enter the correct input.

5. Text in different panels of the page should be searched. For

example if left panel of the web page contains menus and
hyperlinks. Hyperlinks in that area should be searched properly. If
menus are also in scope then they should also appear in the search
results.

6. Search response time should be checked.

7. Try pressing “Enter” key instead of clicking “Search” button.

8. Try searching in the page where a part of the page has form with
Submit button.

Search results testing

DO not ignore the search results just because you got the results.
1. Check number of results in each page.

2. Check the count of the search results displayed in the page.

3. Check if the search results are displayed by popularity or most

viewed or any other criteria mentioned in the requirements.

4. Proper messages should be displayed when there are no results.

5. Each search result should contain one link and few lines
containing the searched keyword. Link should navigate to the page
where the keyword exists.

6. Searched keyword should be highlighted in the search results

page and also in the page where the keyword exists.

7. Pagination of the search results should be tested.

8. Number of search results display and the count should also be

tested.

Test Scenarios for Result Grid

1. Page loading symbol should be displayed when it’s taking more

than default time to load the result page

2. Check if all search parameters are used to fetch data shown on

result grid
3. Total number of results should be displayed on result grid

4. Search criteria used for searching should be displayed on result

grid

5. Result grid values should be sorted by default column.

6. Sorted columns should be displayed with sorting icon

7. Result grids should include all specified columns with correct

values

8. Ascending and descending sorting functionality should work for

columns supported with data sorting

9. Result grids should be displayed with proper column and row

spacing

10. Pagination should be enabled when there are more results than
the default result count per page

11. Check for Next, Previous, First and Last page pagination
functionality

12. Duplicate records should not be displayed in result grid

13. Check if all columns are visible and horizontal scroll bar is
enabled if necessary

14. Check data for dynamic columns (columns whose values are
calculated dynamically based on the other column values)

15. For result grids showing reports check ‘Totals’ row and verify
total for every column

16. For result grids showing reports check ‘Totals’ row data when
pagination is enabled and user navigates to next page

17. Check if proper symbols are used for displaying column values
e.g. % symbol should be displayed for percentage calculation

18. Check result grid data if date range is enabled

20 Scenarios for Testing
login Pages & Search
Functionalities

I recently had a conversation with a prospect and when I

mentioned website UX testing to him, he paused and asked
me with a dubious tone, “Why does a website need UX
testing?”
I explained to him that, few major reasons why UX testing is
so important is because improved user experience ensures
customer satisfaction, retention & product promotion through
mouth publicity. If the users cannot find what they are
looking for on one website, they will inevitably move on to
the next with the same product offering. So even if a site
looks breathtaking and gets lots of bell and whistles for it, if
the user can’t figure out how to use it, he is bound to move
on. 

While explaining this to him, it struck me that, UX testers often invest time and efforts to test some of the most complex scena

In this blog, we provide a handy list of 20+ test scenarios

which are a must-add to the list of test cases – specifically for
testing login page and search functionality.   

Login Scenarios:

GUI & Functionality:

1. Minimum and Maximum lengths should be set for all the

text boxes
 2. Password should be displayed in masked format rather
than showing actual text format

3. Login credentials in UPPER case should not be treated as

invalid

4. Validation message should be shown when special

characters are entered in the username field, or when
invalid username and/or password is entered or the fields
are left blank

5. Reset button should clear data from all the text boxes in
the form

6. Login credentials, especially password, should be stored

in database in encrypted format

Security:

1. When logged in user copy URL and paste in new browser

window, it should redirect to Login page

2. Users should not be allowed to copy and paste Password

from text box

3. Notification email for multiple device login - if user login

from unusual device/machine

4. Entering Login credentials using virtual keyboard should

be provided for banking application

5. After 3 or 5 unsuccessful attempts of login, user login

credentials should get locked for specific period e.g. 24
hours
 6. SSL certificate should be implemented/installed for
Secured Website

7. SQL injection attacks & XSS should be verified for login

8. Two-way authentication through OTP on mobile/email

should be tested for banking application

Session:

1. After logout if user clicks on back button user should not

be able to login within same session, it should redirect to
login page

2. If user logged in on multiple devices and Logout from

one device then it should Logout from all platform/devices

3. Maximum Session out time should be set for Secured

website

Browser:

1. If Browser cookies are cleared and user tries to login, the

system should ask for credentials again

2. ‘Remember Form Data’ setting of the browser should not

remember the password

3. Validate the login functionality when browser cookies

are turned OFF
Search Scenarios

1. Search results displayed should be relevant to search

keyword

2. % sign in search keyword should not redirect to 404

ERROR

3. Application should not crash if user inserted % in search

field

4. When user start typing word in text box it should

suggest words that matches typed keyword

5. There should be pre-defined search criteria for auto

complete e.g. after typing first 3 letter it should suggest
matching keyword

6. When user clicks on any link from result and navigates

back, then result should be maintained

7. After clicking Search field - search history should be

displayed (latest search keyword)
8. All search keyword/filters should get cleared on clicking
Reset button
9. Search results should be cleared on clicking clear search
button
10. History displayed in search field should be relevant to
logged in user only

11. Pagination should be tested for searches returning high

number of records

12. Total number of search records/results should be

displayed on page

13. Search keyword should get highlighted with color in the

search results

14. For ecommerce sites - search keyword should suggest

similar kind of product/items
15. For Advanced Search - limited search filters should be
provided

16. Water text should be provided for user to understand

what to search

17. Validate search rules defined for “Exact Match” with

the search key word

18. Validate search rules defined for “Similar Match” with

the search key word
19. Validate search rules defined to search with a set of
keywords
20. User should be able to search when he enters the
keyword and hits ‘Enter’ button on keyboard
Placement & UI of
Search Bar

– Website Search Bar location is very

essential. Usually it is in the Header
section on top right portion of the screen.

– Look & Feel and Size of the Search Box. Is

it attractive and engaging enough to make
you perform a search instead of roaming
on website pages?

 Is Placeholder text(displayed within the

search box and disappear when you start
typing) is enabled?

– Is font family used in search keyword

matching overall theme and layout?

Is Site Search
Suggestions Enabled?
– Is your website search having auto
suggest feature?

– How smoothly it populates the list of

suggestions as you starts typing into the
search box?

– Are the suggestions properly updated

when you enter / remove a keyword?

– Are the suggested results relevant to the

keyword you are typing?

– What happens when you click on any

suggestion? Is it redirecting to proper
result page?

Advance Search Feature

– Is your website having Advance Search
feature?

– How can you access advance search

window? Is it feasible and user friendly?

– What are the options and extra features

it provides? Are all the features working
properly and producing appropriate search
results?

– Combination of different search criteria

must produce proper results. Same applied
for individual selection.

– Searching through Advance features

should not populate 0 Result. If there is a
case, that particular criteria should be
hidden.

Search Results

– What happens when you click Search

button without entering any keyword?
– Does the search box keeps the history of
previously searched keywords?

– Are you getting the proper result for what

you have searched?

– Do the result page title contains

searched keyword?

– How many search results are displayed

per page? Is pagination enabled when you
have more results per page?

– In which order the search result is

organized? Can you change the order?
– Is there a facility to search again from
result page itself?

– There must not be any discrepancy in

result when searching with same keyword
multiple times.

– How good is the performance of

rendering results for most frequently used
search keywords?
– What happens when you search with a
keyword that does not produce any result?
There must be a page showing you proper
message with a box to search again.

– How feasible it is for user to navigate

back to same search result page after
clicking on any result link?

Responsive is Must
– Are you able to see each and every
feature of Search in responsive mode?

– How user friendly is Search in Mobile

devices? It must not be frustrating.

– Is Advance search working properly in

responsive mode?

– All the images and visuals in Search

result should be properly displayed in
responsive screen.

– Almost every point we discussed above

applies for responsive mode as well.

So, that is all I can think of right now. I will

be adding more scenarios in future. You
can also help me make this list richer, post
a comment if you feel any scenario
deserves to be in the list which I have
missed.

Thank You & Happy Testing!!

Test Cases of Google
Search
1. Verify that the response fetched for a
particular keyword is correct and related
to the keyword, containing links to the
particular webpage
2. Verify that the response are sorted by
relevancy in descending order i.e. most
relevant result for the keyword are
displayed on top

3. Verify that response for multi word

keyword is correct

4. Verify that response for keywords

containing alphanumeric and special
characters is correct

5. Verify that the link title, URL and

description have the keyword
highlighted in the response
6. Verify auto-suggestion in Google e.g.
providing input as ‘fac’ should give
suggestions like ‘facebook’, ‘facebook
massenger’, ‘facebook chat’ etc
7. Verify that response fetched on
selecting the suggested keyword and on
providing the keyword directly should be
same
8. Verify that the suggestion provided by
Google are sorted by most
popular/relevant suggestions
9. Verify that user can make search
corresponding to different categories –
web, images, videos, news, books etc
and response should correspond to the
keyword in that category only
10. Verify that misspelled keyword
should get corrected and response
corresponding to the correct keyword
should get displayed

11. Verify that multi word misspelled

keywords also get corrected

12. Verify the performance of search-

check if the time taken to fetch the
response is within the ballpark
13. Verify that total number of results
fetched for a keyword
14. Verify that the search response
should be localised that is response
should be more relevant to the
country/area from which the search
request is initiated
15. Verify Google calculator service-
make any arithmetic request, calculator
should get displayed with correct result
16. Verify Google converter service-
make request like- 10USD in INR and
check if the result is correct

17. Verify search response for a large

but valid strings

18. Verify that incorrect keywords –

keywords not having related result
should lead to “did not match any
documents” response

19. Verify that user can make search

using different languages
 20. Verify that for a keywords, some
related search terms are also displayed
to aid user’s search
21. Verify that for number of results
more than the limit on a single page,
pagination should be present, clicking
on which user can navigate to
subsequent page’s result
22. Verify Google’s advanced search
options like- searching within a website,
searching for files of specific extension
23. Verify if the search is case-
insensitive or not
24. Verify the functionality of “I’m feeling
Lucky” search- the top most search
result should get directly returned (but
as of now google doodle page link is
displayed)

Front End – UI Test

Cases of Google
Search
1. Verify that Google Logo is present
and centre aligned

2. Verify that the search textbox is

centre aligned and editable

3. Verify that search request should get

hit by clicking on search button or hitting
enter after writing the search term

4. Verify that in the search result-

webpage’s title, URL and description are
present
5. Verify that clicking the search result
will lead to the corresponding web page
6. Verify that pagination is present in
case number of results are greater than
the maximum results allowed in a page
7. Verify that user can navigate to a
page number directly or move to
previous or next page using the links
present
8. Verify that different languages links
are present and gets applied on clicking
the same
9. Verify that the total number of results
for the keyword is displayed

10. Verify that the time taken to fetch the

result is displayed
 20 Useful Test Cases for testing User Interfaces

Required Fields - If the screen requires data entry on a specific 
field, it is good practice to identify the required fields with a red 
asterisk and to give a friendly warning if the data is left blank.

Data Type Errors - If the screen contains dates, numeric, 

currency or other specific data types, ensure that only valid data 
can be entered.
Field Widths - If the screen contains text boxes that allow data 
entry, ensure that the width of data entered does not exceed the 
width of the table field (e.g. a title that allows 100 characters in 
the database should not allow more than 100 characters to be 
entered from the user interface).
Onscreen Instructions - Any screen that is not self-explanatory 
to the casual user should contain onscreen instructions that aid 
the user.
Keep Onscreen Instructions Brief - While onscreen 
instructions are great, keep the wording informative, in layman's 
terms, but concise.
Progress Bars - If the screen takes more than 5 seconds to 
render results, it should contain a progress bar so that the user 
understands the processing is continuing.
Same Document Opened Multiple Times - If your application 
opens the same document multiple times, it should append a 
unique number to the open document to keep one document 
from overwriting another. For example, if your application opens 
a document named Minutes.txt, if it opens the same document 
for the same user again, consider having it append the time to 
the document or sequentially number it (Minutes2.txt or 
Minutes_032321.txt).
Cosmetic Inconsistencies - The screen look, feel and design 
should match the other screens in your application. Creating and 
using a style guide is a great way to ensure consistency 
throughout your application.
Abbreviation Inconsistencies - If your screens contain 
abbreviations (e.g. Nbr for number, Amt for amount, etc), the 
abbreviations should be consistent for all screens in your 
application. Again, the style guide is key for ensuring this.
Save Confirmations - If your screen allows changing of data 
without saving, it should prompt you to save if you move to 
another record or screen.

Delete Confirmations - If a person deletes an item, it is a good 
idea to confirm the delete. However, if your user interface allows 
deleting several records in a row, in some cases you might 
consider allowing them to ignore the confirmation as it might get 
frustrating to click the confirmation over and over again.

Type ahead - If your user interface uses combo boxes (drop 

down lists), be sure to include type ahead (if you have hundreds 
of items in a list, if you type in the first letter it will skip to the 
first item that begins with that letter).
Grammar and Spelling - Ensure that you have test cases that 
look for grammar or spelling errors.
Table Scrolling - If your application lists information in table 
format, if the data in the table extends past one page, the 
scrolling should scroll the data but leave the table headers in 
tact.
Error Logging - If fatal errors occur as users use your 
application, ensure that your applications writes those errors to a 
log file, event viewer or a database table for later review. Log the 
routine the error was in, the person logged on, and the date/time 
of the error.
Error Messages - Ensure that error messages are informative, 
grammatically correct, and not condescending.
Shortcuts - If your application allows short cut keys (like 
CTRL+S to save), test each shortcut to ensure it works in all 
different browsers (if the application is web based).
Invalid Choices - Do not include instructions for choices not 
available at the time. For example, if a screen cannot be printed 
due to the state of the data, the screen should not have a Print 
button.
Invalid Menu Items - Do not show menu items that are not 
available for the context you are currently in.
Dialog Box Consistency - Use a style guide to document what 
choices are available for dialog boxes. You should have not have 
Save/Cancel dialog on one screen and an OK/Cancel on another, 
this is inconsistent.
Basic Tests for the shopping cart and checkout flow in a E-
commerce.
Most E-commerce Websites share a general common theme and
structure in which the shopping cart and checkout flow are the
most important part.
Below are some basic test scenarios related to the shopping
cart and checkout pipeline which needs to be covered
before release.
Shopping Cart:-
Add one item to the cart and verify.
Increase the quantity of the item from the cart and verify.
Add the same item multiple times and verify.
Add multiple items of different types and verify.
Remove some items from the cart and verify.
Remove all items from the cart and then verify.
Click on an item in the cart and verify that the user is
redirected to the product detail page.
Check that the price of the cart is discounted when we apply
a valid coupon.
Check that the price of the cart is not discounted when we
apply an invalid coupon.
Add item(s) to the cart, close the browser and reopen the
same site.
Add item(s) to the cart, close the browser and reopen the
same site.

Verify the product QTY field when the product is out of stock.

Verify that the user is able to add a text note for all products.

Verify that the user is able to add any or all products to his
wishlist by clicking on the wishlist link.
Verify that the user is able to mark his order as a gift.
Verify that the user is able to add any a gift message.
Verify that the user is redirected to the checkout page after
clicking on the checkout button.
Verify the cart total when the exclusive tax is enabled from
the admin end.
Verify the cart total when the inclusive tax is enabled from the
admin end.

Checkout flow:-
Ensure that user can access the Checkout Page only after
adding the product to the cart.

Ensure that Checkout Address Page consists of all the

details of the product such as Name, Quantity, Amount, etc.

Ensure that only registered users are allowed to access the

Checkout Address Page.
Ensure that Name, Street Address, City, State, Country,
Postal code is the mandatory field in the Checkout Address
page (Shipping Address).
Ensure that Name, Street Address, City, State, Country,
Postal code is the mandatory field in the Checkout Address
page (Billing Address).
Ensure that error message is displayed when the user enters
invalid input in all the mandatory field in the checkout
address page.
Ensure that Back to cart link is available so that user can
modify the cart content if needed.
Ensure that user is redirected to Checkout payment page
only after entering valid mandatory details in the checkout
Address page.
Ensure that error message is displayed when the user leaves
any one of the mandatory fields in the checkout Address
page.
Ensure that Next Button and Cancel Button are available in
the Checkout Address Page.
Check that a user is able to apply a valid coupon.
Check order price when the coupon is applied.
Verify the error message for the invalid coupon.
Check that user is able to make his order as a gift.
Ensure that the user is able to add any gift message.
Check order price when gift and wrapping charges are
applicable.
Check the shipping price.
Check the shipping price tax.
Check the payment options.
Ensure that Name on Card, Card Number, Expiration date,
CWW2 are mandatory fields in the Payment Page.

Ensure that error message is displayed when the user enters

invalid input in all the mandatory field on the Payment Page.

Ensure that error message is displayed when the user leaves

any one of the mandatory fields in the Payment Page.

Ensure that the user is redirected to the third party (Vender)

page.
Ensure that the user is redirected to the third party (PayPal)
page if he is going to pay through a third party payment
gateway (PayPal).
Place an order where order total price is Zero (0).
Place an order where the total discount is more than the
entire order.
Place an order by double clicking on the Submit Button.
 Test scenarios for Registration Page
1. Verify that all the specified fields are present on the registration
page
2. Verify that the required/mandatory fields are marked with * against
the field
3. Verify that for better user interface dropdowns, radio buttons and
checkboxes etc fields are displayed wherever possible instead of just
textboxes
4. Verify the page has both submit and cancel/reset buttons at the
end
5. Verify that clicking submit button after entering all the required
fields, submits the data to the server
6. Verify that clicking cancel/reset button after entering all the
required fields, cancels the submit request and resets all the fields

7. Verify that whenever possible validation should take place at client

side
8. Verify that not filling the mandatory fields and clicking submit
button will lead to validation error
9. Verify that not filling the optional fields and clicking submit button
will still send data to server without any validation error
10. Check the upper limit of the textboxes
11. Check validation on date and email fields (only valid dates and
valid email Ids should be allowed
12. Check validation on numeric fields by entering alphabets and
special characters
13. Verify that leading and trailing spaces are trimmed
14. Verify that entering blank spaces on mandatory fields lead to
validation error
15. Verify that after making a request to the server and then sending
the same request again with the same unique key will lead to server
side validation error
Test Scenarios Registration Form [Write Test Cases of Signup Form]

Test Scenarios Registration Form

User Name

First Name

Last Name

Password

Confirm Password

Email Id

Phone number

Date of birth

Gender

Location

Terms of use
Submit
Login (If you already have an account)
Test Scenarios of a Registration Form:
1. Verify that the Registration form contains Username, First Name,
Last Name, Password, Confirm Password, Email Id, Phone number,
Date of birth, Gender, Location, Terms of use, Submit, Login (If you
already have an account)
2. Verify that tab functionality is working properly or not
3. Verify that Enter/Tab key works as a substitute for the Submit
button
4. Verify that all the fields such as Username, First Name, Last Name,
Password and other fields have a valid placeholder
5. Verify that the labels float upward when the text field is in focus or
filled (In case of floating label)
6. Verify that all the required/mandatory fields are marked with *
against the field
7. Verify that clicking on submit button after entering all the mandatory
fields, submits the data to the server

8. Verify that system generates a validation message when clicking

on submit button without filling all the mandatory fields.

9. Verify that entering blank spaces on mandatory fields lead to

validation error
10. Verify that clicking on submit button by leaving optional fields,
submits the data to the server without any validation error

11. Verify that case sensitivity of Username (usually Username field

should not follow case sensitivity – ‘rajkumar’ & ‘RAJKUMAR’ acts
same)

12. Verify that system generates a validation message when entering

existing username
13. Verify that the character limit in all the fields (mainly username
and password) based on business requirement
14. Verify that the username validation as per business requirement
(in some application, username should not allow numeric and special
characters)
15. Verify that the validation of all the fields are as per business
requirement
16. Verify that the date of birth field should not allow the dates greater
than current date (some applications have age limit of 18 in that case
you have to validate whether the age is greater than or equal to 18 or
not)
17. Verify that the validation of email field by entering incorrect email
id
18. Verify that the validation of numeric fields by entering alphabets
and characters
19. Verify that leading and trailing spaces are trimmed after clicking
on submit button

20. Verify that the “terms and conditions” checkbox is unselected by

default (depends on business logic, it may be selected or unselected)

21. Verify that the validation message is displayed when clicking on

submit button without selecting “terms and conditions” checkbox

22. Verify that the password is in encrypted form when entered

23. Verify whether the password and confirm password are same or
not
Before We Start Testing the Sign-Up Pages
So before moving with the test cases, we need to gather some
requirements like:

First Name

Last Name

User Name

Email ID

Phone Number
Password
Confirm Password
Address
Gender
The fields may also vary according to your registration process. I have
tried to cover the maximum possibilities for a sign-up page.
WorkFlow of Testing a Sign-Up Page
1. Enter the necessary fields: Name, Email ID, Password, Confirm
Password
2. Validate the fields:
Email
Password: Should have 8 to 16 characters, must contain one
special character, at least one uppercase character, and have a
numerical.
Phone number: Country code is required, only numbers are
allowed.
3. Verify the email ID: Send verification to the entered Email ID
after a successful validation
 4. * should be there on the mandatory fields.
APIs Issues in a Sign-Up Page

The major challenge you’ll face here is to test all possible scenarios
for all the possible combinations of browsers, devices, and OSes.
Because as we know that the sign-up process makes use
of APIs and API compatibility in browsers needs to be taken care of.
So, many times, you’ll find that your sign up is working on a browser
but when a user tries to do the same from any other browser or
device it will fail.

Browser Incompatibility: Authentication Problems in a Sign-Up

Page

If a sign-up page uses strong authentication techniques like second-

factor authentication utilizing text SMS verification (or without that),
password-less authentication, or encrypted public key, then there
might be a possibility of cross browser compatibility issues in
authentication. Because these techniques make use of APIs like web
authentication API, the problem that occurs here is that these
APIs are unsupported in various browsers.

So, authentication will fail on browsers like IE, older edge versions,
older Chrome, and Firefox versions, Safari, iOS Safari, Opera Mini, UC
Browser, and Samsung internet. So, if a user tries to sign up using this
browser, they will not be able to finish it off. So, you need to test for
these browsers and make sure that the authentication works on all
browsers.

Payment APIs in a Sign-Up Page

There are many websites that ask for payment details or card
validation details on sign up. So, the registration or sign up may fail if
the payment is not processed successfully or the card is not validated.

Developers make use of APIs like Payment Request API for

allowing web pages to switch information from the user agent. This is
basically done when the user agent provides input before it approves
or denies a payment request. This API again comes with some
incompatibility issues.

So, you need to test the payment process for all browsers.
Animations API for a Sign-Up Page

While designing a sign-up page, we make sure of creating a beautiful

design by adding some beautiful animations on the buttons for sign
up. However, sometimes, this might cause a huge problem.

APIs like Web Animations API allow you to synchronize and

change timings of a web page (animations of DOM elements),
sometimes causing compatibility issues in browsers.
As you can see, APIs hold a major portion of compatibility issues in a
sign-up process. So, it’s important to test APIs and overall page
functionalities as well for a sign-up page along with the mentioned
test cases for a sign-up process on all browsers and browser versions.

Test Cases for a Sign-Up Page

Buttons
Check all buttons, radio buttons, checkboxes by clicking on all
buttons and see if they are working or not.
Required Fields
Check all required fields by not entering the data and (*) should be
shown asking for mandatory field.

Check all required fields by entering the data and validating. Upon
entering the all required fields User should be signed up, a
successful registration message should be sent along with a mail.

Optional Fields
Check all optional fields by entering the data and a successful
registration should happen.
Check all optional fields by not entering the data, and again, the
user should be successfully registered without asking for the
optional fields.
Check by filling some optional fields and leaving some, and the
user should be successfully registered without asking for the
optional fields.
Email Validation
Test for some invalid emails with cases like: without @, without(.),
without a domain, and without alphabets before @. In such cases,
the user should be prompted to enter a valid email address and
the user shouldn’t be signed up.
Test for valid email addresses by entering valid email addresses
and then click on sign-up. The user should be registered
successfully.
Test for valid but already existing email address. The user should
not be signed up and prompted to log in instead.
Phone Number Validation
 Test for non-numeric inputs by entering some alphabets or special
characters. Since it’s a number field, it should show an error and
ask the user again to enter the correct phone number.
Test for numeric inputs by entering a valid number and clicking on
sign-up. The user should be registered successfully.
Test for input with country code applied by entering a number
starting from + followed by dial code. The user must not get any
error message on that.
Password Validation
Check the password for less value than the minimum characters
specified. Enter a password of fewer than 8 characters and then
click on sign up. The user should see a message to enter a value
between 8 to 16 characters and shouldn’t be signed up.

Check the password for more value than the maximum characters
specified. Enter a password of more than 16 characters and then
click on sign up. The user should see a message to enter a value
between 8 to 16 characters and shouldn’t be signed up.

Enter a password without alphanumeric characters and click on

sign up. It should prompt the user to enter a password having
alphanumeric characters.
Check by entering an alphanumeric password between 8-16
characters and a special character. It should not give any error and
sign up should be successful.
User Interface
Tab functionality should work fine. Check by pressing tab button.
It should navigate between the fields.
Enter button should act as a substitute for click on the sign-up
button and the user should be successfully signed up on pressing
enter.
Verify that the cursor should change according to the fields. On
text fields, it should be a ⌶; on buttons, it should be a hand
pointer.
How to test drop down lists on websites?
Ensure the design of the drop-down i.e. its alignment with other items on the page on all common browsers.
Ensure that the drop-down accommodates the longest text within its boundary.
Ensure that the drop-down can be scrolled down on clicking the down arrow.
Ensure that the drop-down has a proper title.
Ensure that the default item is getting displayed when the user first visits the page.
Ensure that on clicking the down arrow all items are getting listed in its expected order.
Ensure the spelling, font and style of the text inside the drop-down.
Ensure that on clicking the categories, the page displays the corresponding items.
Ensure that the selected category is getting highlighted on selecting the item.
Ensure the time taking in loading the items under each category. Too much time should not be taken for loading th
items.
If the list (of items) of this drop-down is controlled by some other selection (say in another drop-down or check-bo
radio-button) then ensure the correctness of the items in this drop-down.
If the selection in this drop-down is controlling some other control (say, enabling/disabling etc) then check the pro
action.
Ensure that on pressing an alphabet on the keyboard, categories starting with that alphabet is getting highlighted.
Ensure that the user is able to select the categories/items by pressing the down key on the keyboard.

While testing drop-down it is of foremost importance that you ensure the design of the drop-down on all browsers.
compatibility testing is an important factor, since the design/alignment of the drop-down may change on various b
which is a commonly noted issue. Since drop-down is a simple and common feature that we come across on a
websites, I hope this article will help you. Feel free to contribute your suggestions. If you have additional test cases
topic, do contribute. Enjoy testing:)
 Test Cases for sliders.
Slider Testing.
Following are the test cases to be considered while testing slider.
Ensure the design of the slider on all browsers (browser compatibility).
Ensure the smoothness and automatic loading of the slides.
Ensure that the slider are getting loaded (manually) when the user clicks the
right arrow on the slides.
Ensure the order of the slider images.
Ensure whether the slides can be clicked and thumbnail is getting displayed
on mouse overing.
Ensure whether five buttons (the number is as per the requirement)
corresponding to each slideshow image is displayed below the slideshow (to
the right).
Ensure whether on clicking each button, the corresponding slideshow image
is displayed.
Ensure whether each button below the slideshow is highlighted when the
corresponding image is loaded.

Ensure whether the time interval of slideshow is same for all the images.

Ensure whether on clicking each image of the slideshow, the corresponding

page is displayed.
Ensure whether administrator (or role who has permission to
configure/manage the display of slideshow) is able to change the image and
the url of the slides.
Ensure corresponding image should not get crop.
If Slider is containing a thumbnails of slides check clicked image only open
and should get focus.
Ensure slider image and title are displayed same which required.
Ensure slider width and height.
 Test cases for Checkbox

Here are some of the test cases for the checkboxes.

1. Check if the checkbox is selectable or not.

2. Check if the checkbox selection enables the specific
element as selected by mouse pointer or keyboard
selection.

3. Check if the checkbox is selected and pressing

submit redirects to the option as per the choice made.
4. Check if the checkbox selection is properly
recorded in database or for browser redirection.
5. Uncheck one checckbox and select another and
click on submit and verify if different choice is
considered in redirection.
6. Check if the checkbox alignment on the form page
is proper or not.
7. Check if the label for the checkbox is properly
aligned.
8. Check if the multiple checkboxes can be selected or
not.
9. Check if the checkboxes selected one at a time or
multiple at a time are as per the requirement of the
application.
10. Check if the corresponding data is selected by the
database based on the selection.
11. Check if the validation controls enabled or
triggered if no user action is done on the choices.
12. Verify if the selection control is inactive when the
page is loaded.
13. Verify if the initial focus of the checkbox is on the
first checkbox.
14. Verify if the checboxes are placed in a order.
15. Verify the physical location of the checkboxes
(X.Y Coordinates, Height, Lenght, Width).
• Test cases/scenarios for Messages and pop up – Messages
are guidance or alert for user so it is very necessary at every
point messages should be given for user
a. Check Message For Each field of an web app
b. Check informative message should display standard icon,
message content, cross and ok button
c. Check all text messages for spelling and grammar
d. Confirmation Messages
e. Pop up Messages
f. Messages as per Browser
g. Error Messages
h. Alert/Error message should be shown in red color
i. Check all alert messages should display question mark
j. Confirmation message of Successful Functionality Should be
shown in Green color
k. Confirmation Before Delete functionality
l. Font, Alignment, Size and color of the Messages
m. Placing & Spacing Of Messages
n. Format of messages
o. Spellings of messages
p. While Message Pop up or a child window opens for message
other areas will get Non editable.
q. Most important Message Should be easily understandable
r. Time must be Such as the message can be read by User
s. Messages must be related to concern page only it should get
disappear once on new page
• Test cases/scenarios for Links – There are two
types of link can be available on web page that is
internal and external links here are some test
scenarios to test link on web page
a. Tool tips text should be available and meaningful.
b. Check whether all external links are opening in new
window with proper URL
c. Test all internal links are navigating within
application as per requirement
d. Test links jumping on the same pages
e. Check whether email address link opening the mail
instance like outlook
f. Test to check if there are any blank page to link
g. Test Links opening in other tab /window as per
requirement
h. Compatibility Testing for all links on other browsers
i. Ensure that color of links change after the page is
visited once. (This can vary as per the design).
j. Ensure that the link color is as per the specification.
k. Ensure that a hand icon is displayed when mouse
pointer is hovered over the link.
l. Check loading time for internal links as per
requirement
m. Check whether shared link is getting shared
properly with correct address
n. Check whether shared link is getting opened
properly
 Return Policy

If, within 45-days after delivery of your purchase from definitivetechnology.com,

you are not completely satisfied, please call 800-228-7148 option 2 to inform us
that you want to return your product. We will give you return shipping
information. You must return the product to us in its original packaging and
include all accessories. Once we receive the product in our warehouse, we will
give you a complete refund.

Note: all returns must include your assigned Return Authorization number

If you return a product purchased using a promotional discount, your refund will
equal the amount you paid for the product.

If you return a product purchased using a bundle promotional discount you must
return all items in the bundle to receive a full refund, and your refund will equal
the amount you paid for the product bundle. If the complete bundle is not
returned, your refund will equal the amount your paid for the product bundle less
the MSRP of the item(s) not returned.

Cancellation Policy
Our system is designed to fulfill orders as quickly as possible. As a result, we
cannot cancel or change an order once it has entered the shipping process and is
"in progress."
 Test Scenarios of a Registration Form:
1. Verify that the Registration form contains Username, First
Name, Last Name, Password, Confirm Password, Email Id,
Phone number, Date of birth, Gender, Location, Terms of use,
Submit, Login (If you already have an account)
2. Verify that tab functionality is working properly or not
3. Verify that Enter/Tab key works as a substitute for the Submit
button

4. Verify that all the fields such as Username, First Name, Last
Name, Password and other fields have a valid placeholder

5. Verify that the labels float upward when the text field is in
focus or filled (In case of floating label)
6. Verify that all the required/mandatory fields are marked with *
against the field
7. Verify that clicking on submit button after entering all the
mandatory fields, submits the data to the server

8. Verify that system generates a validation message when

clicking on submit button without filling all the mandatory fields.

9. Verify that entering blank spaces on mandatory fields lead to

validation error

10. Verify that clicking on submit button by leaving optional

fields, submits the data to the server without any validation error

11. Verify that case sensitivity of Username (usually Username

field should not follow case sensitivity – ‘rajkumar’ &
‘RAJKUMAR’ acts same)
12. Verify that system generates a validation message when
entering existing username
13. Verify that the character limit in all the fields (mainly
username and password) based on business requirement
14. Verify that the username validation as per business
requirement (in some application, username should not allow
numeric and special characters)
15. Verify that the validation of all the fields are as per business
requirement
16. Verify that the date of birth field should not allow the dates
greater than current date (some applications have age limit of
18 in that case you have to validate whether the age is greater
than or equal to 18 or not)
17. Verify that the validation of email field by entering incorrect
email id
18. Verify that the validation of numeric fields by entering
alphabets and characters
19. Verify that leading and trailing spaces are trimmed after
clicking on submit button
20. Verify that the “terms and conditions” checkbox is
unselected by default (depends on business logic, it may be
selected or unselected)
21. Verify that the validation message is displayed when
clicking on submit button without selecting “terms and
conditions” checkbox
22. Verify that the password is in encrypted form when entered
23. Verify whether the password and confirm password are
same or not