Scribd
Upload
155 views14 pages

Test Scenario

A test scenario is any functionality that can be tested to represent real-world user scenarios. Scenario testing uses scenarios to test complicated systems more easily. Test scenarios ensure complete test coverage, help determine test effort, and allow end-to-end program functioning to be studied. Scenarios may not be created for agile projects or bug fixes where scenarios are already documented. Scenarios are written by understanding requirements and envisioning user actions and objectives.

Uploaded by

Rahul Chauhan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
155 views14 pages

Test Scenario

A test scenario is any functionality that can be tested to represent real-world user scenarios. Scenario testing uses scenarios to test complicated systems more easily. Test scenarios ensure complete test coverage, help determine test effort, and allow end-to-end program functioning to be studied. Scenarios may not be created for agile projects or bug fixes where scenarios are already documented. Scenarios are written by understanding requirements and envisioning user actions and objectives.

Uploaded by

Rahul Chauhan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Manual Testing

What is Test Scenario ?


What is a Test Scenario?

 A TESTSCENARIO is defined as any


functionality that can be tested.

 Asa tester, you should put yourself in


the end user’s shoes and figure out
the real-world scenarios and use
cases of the Application Under Test.
What is Scenario Testing?

 ScenarioTesting is a variant of
Software Testing where Scenarios
are Used for Testing. Scenarios
help in an Easier Way of Testing of
the more complicated Systems
Why create Test Scenarios?

 Creating Test Scenarios ensures complete


Test Coverage.

 They serve as a quick tool to determine the


testing work effort and accordingly create a
proposal for the client or organize the
workforce.

 For studying the end-to-end functioning of


the program,
When not create Test Scenario?

 Projects that follow Agile Methodology like


Scrum, Kanban may not create Test
Scenarios.

 Test Scenario may not be created for a new


bug fix or Regression Testing. In such
cases, Test Scenarios must be already
heavily documented in the previous test
cycles. This is especially true for
Maintenance projects.
How to Write Test Scenarios
 Step 1: Read the Requirement Documents
like BRS, SRS of the System Under Test
(SUT).  You could also refer uses cases,
books, manuals, etc. of the application to
be tested.

 Step 2: For each requirement, figure out


possible users actions and objectives.
Determine the technical aspects of the
requirement. Ascertain possible scenarios
of system abuse and evaluate users with
hacker's mindset.
 Step 3: After reading the Requirements
Document and doing your due Analysis, list
out different test scenarios that verify each
feature of the software.

 Step 4: Once you have listed all possible Test


Scenarios, to verify that each & every
requirement has a corresponding Test
Scenario

 Step 5: The scenarios created are reviewed by


your supervisor. Later, they are also reviewed
by other Stakeholders in the project.
Example 1: Test Scenario for eCommerce Application

 Test Scenario 1: Check the Login


Functionality
 Test Scenario 2: Check the Search
Functionality
 Test Scenario 3: Check the Product
Description Page
 Test Scenario 4: Check the Payments
Functionality
 Test Scenario 5: Check the Order History
Apart from these 5 scenarios here is the
list of all other scenarios
 Check Home Page behavior for returning
customers
 Check Category/Product Pages
 Check Customer Service/Contact Pages
 Check Daily Deals pages
UI Test Scenarios for Login Page
 Verify that all the labels and controls
including text-boxes, buttons, and links are
present on the Login page.
 Verify that the font type and size of the labels

and the text written on the different elements


should be clearly visible.
 Verify that the size, color, and UI of the

different elements are as per the


specifications. 
 Verify that the application’s UI is responsive

i.e. it should adjust to different screen


resolutions and devices.
Functional Test Scenarios for Login Page
 Verify that as soon as the login page opens, by
default the cursor should remain on the username
textbox.
 Verify that the user is able to navigate or access

the different controls by pressing the ‘Tab’ key on


the keyboard.
 Verify that the password is in masked form when

entered.
 Verify if the password can be copy-pasted or not.
 Verify that the user is able to login by entering

valid credentials and clicking on the ‘Login’ button.


 Verify that the user is able to login by entering

valid credentials and pressing Enter key.


 Verify that the user is not able to login with an invalid
username and password.
 Verify that the validation message gets displayed in
case the user leaves the username or password field
as blank.
 Verify that the validation message is displayed in the
case the user exceeds the character limit of the user
name and password fields.
 Verify that reset button functionality on the login
page. Clicking on it should clear the textbox’s
content.
 Verify if there is a checkbox with the label “remember
password” on the login page.
 Verify that closing the browser should not log-out an
authenticated user. Launching the application should
lead the user to login state only.
Security Test Scenarios of login page
 Verify that there is a limit on the total number
of unsuccessful login attempts. So that a user
cannot use a brute-force mechanism to try all
possible combinations of username-password.
 Verify that in case of incorrect credentials, a
message like “incorrect username or password”
should get displayed instead of an exact
message pointing to the incorrect field. This is
because a message like “incorrect password”
will help a hacker in knowing that the username
is correct and he just needs to try a different
combination on the password field only.
 Verify the login session timeout duration.
So, that once logged-in a user cannot be
authenticated for a life-time.
 Verify that once logged in, clicking the back

button doesn’t logout the user.

You might also like