Scribd
Upload
37 views38 pages

Manual Testing Slides

The document outlines the process of creating test scenarios, emphasizing the importance of understanding user requirements and mapping them to test cases. It provides examples of test scenarios for functionalities such as login and search, as well as guidelines for writing test cases and defect reports. Additionally, it categorizes defects by severity and type, offering a structured approach to testing and quality assurance.

Uploaded by

Ahmed Mawrdy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
37 views38 pages

Manual Testing Slides

The document outlines the process of creating test scenarios, emphasizing the importance of understanding user requirements and mapping them to test cases. It provides examples of test scenarios for functionalities such as login and search, as well as guidelines for writing test cases and defect reports. Additionally, it categorizes defects by severity and type, offering a structured approach to testing and quality assurance.

Uploaded by

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

Test scenarios

Test Scenario

A TEST SCENARIO is defined as any functionality that can be tested. It is also called Test
Condition or Test Possibility. As a 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.
How to create a test scenario
1. Carefully study the Requirement Document – Business Requirement Specification (BRS),
Software Requirement Specification (SRS), Functional Requirement Specification (FRS)
pertaining to the System Under Test (SUT).

1. Isolate every requirement, and identify what possible user actions need to be tested for it.
Figure out the technical issues associated with the requirement. Also, remember to analyze
and frame possible system abuse scenarios by evaluating the software with a hacker’s eyes.

1. Enumerate test scenarios that cover every possible feature of the software. Ensure that these
scenarios cover every user flow and business flow involved in the operation of the website or
app.

1. After listing the test scenarios, create a Traceability Matrix to ensure that every requirement is
mapped to a test scenario.

1. Get the scenarios reviewed by a supervisor, and then push them to be reviewed by other
stakeholders involved in the project.
4

Let’s write test scenarios for the login functionality


You can ask those questions: 5

• Can the user log in with a valid email id and password?

• What happens when user enters an invalid email id and valid password?

• What happens when a valid email id and invalid password are entered?

• What happens when an invalid email id and invalid password is entered?

• What happens when the email id and password fields are left blank and the
Login button is clicked?

• Is the Forgot password? option working as expected?

• Is every link on the page working as expected?


6

Sample Login Test Scenarios:

1. Login with valid Email & Password


2. Login with valid Email & invalid password
3. Login with invalid Email
4. Test Forgot password functionality
5. Check show password button
6. Test Remember me option
7

Let’s write test scenarios for the search functionality


Search Test Scenarios 8

1. Search results displayed should be relevant to search keyword


2. When user starts typing a word in text box, it should suggest words that match typed keyword
3. There should be pre-defined search criteria for auto complete e.g. after typing first 3 letter it should suggest
matching keyword
4. After clicking Search field - search history should be displayed (latest search keyword) Search results
should be cleared on clicking clear search button
5. History displayed in search field should be relevant to logged in user only
6. Pagination should be tested for searches returning high number of records
7. Total number of search records/results should be displayed on page
8. Search keyword should get highlighted with color in the search results
9. For ecommerce sites - search keyword should suggest similar kinds of products/items
10. For Advanced Search - limited search filters should be provided
11. Validate search rules defined for “Exact Match” with the search key word
12. Validate search rules defined for “Similar Match” with the search key word
13. Validate search rules defined to search with a set of keywords
14. User should be able to search when he enters the keyword and hits ‘Enter’ button on keyboard
9

Try to create test scenarios for Gmail Registration


Test Case Writing
What is a Test Case

A set of preconditions, inputs, actions (where applicable), expected results, developed


based on test conditions.
1.Test Case Title:

• Verify login with a valid username & password


2-Precondition:

• User is already registered using valid credentials


3-Test Steps:

1. Enter a valid username


2. Enter a valid password
3. Click on Sign in
4-Expected Result:

• User is logged in successfully and redirected to (XYZ) page


5-Test Scenario (Test Suite)

• Login
6-Test Environment

• Windows 10 – Chrome – Wi-Fi


• Samsung Galaxy Note 10 - Android 10 – 4G Network
• iPhone 11 – iOS 13.3.1 – 5G Network
7-Actual Result

• Very important note: Never fill the actual result field until you execute the test case
8-Status
Sample Test Case
21

Write 4 test cases for Gmail Registration with all required fields
Defect Reporting
What is a defect report?

Documentation of the occurrence, nature, and status of a defect


What is a defect?

An imperfection or deficiency in a work product where it does not meet its requirements
or specifications. [Synonyms: bug, fault]
1-Bug Report Title:

• Section -> Description


• Register -> No error message appears when user leaves password field empty
2-Steps to reproduce

• Must be very specific


• Ex:
1. Open www.facebook.com
2. Click on the hamburger icon in the upper left corner
3. Scroll down to the bottom of the screen
4. Click on Settings
5. Click on data usage
6. Change data usage to “minimum limit”
3-Expected Result

• The same expected result as in the test case


4-Actual result

• What really happened when the steps are executed


5-Test environment

• Specify the environment(s) in which the defect occurred

• Windows 10 – Chrome – Wi-Fi


• Samsung Galaxy Note 10 - Android 10 – 4G Network
• iPhone 11 – iOS 13.3.1 – 5G Network
6-Screenshot or video:

• The screenshot must show the whole screen


• A red rectangle should be around the defect area
• The video should show the clicks on the keyboard
7-Bug Severity

• Critical: Login isn’t working-Application crashes in Home page – Wrong cart value

• High: Login page responds slowly – User is not able to add profile image

• Medium: Some pages have poor performance- Portrait mode isn’t working correctly

• Low: Spelling mistakes – Image misalignment


Types of defects
1-Functional

• Forgot password functionality isn’t working


2-Visual (UI)
Non functional
3-Content
Non functional
4-Performance
Non functional

• Video takes too much time to play


5-Suggestion/Enhancement
Non functional

• The font of the placeholder should be bigger


Sample Defect Report

Title Login -> Forgot password button is not working

Steps to reproduce 1- Navigate to login page


2- Click on forget password button

Expected Result The button should be clickable and redirecting to “forgot


password” page

Actual Result Button is not clickable and nothing happens when clicking it

Test Environment Samsung galaxy note 10 - Android 10 - 4G network

Severity High

Type Functional

Screenshot

You might also like