Types of Testings :-

There are two types of Testings:

1.Functional Testing : Manual Testers+ Automation Testers-----Automation Testers-Client Req--—

Manual Testers and Automation Testers
In this type of testing , one will test the Behavior the application as per the client requirements.

In the process of developing the application we can perform Functional testing/Before developing the
application itself we have to perform it

1.Test Associate--Freshers

2.Test Engineer/Software Test engineer

3.Senior Test Engineer

4.Test Lead----5 Experience

5.Functional Consultant—7 Years

2.Non-Functional Testing:---
1.After Completion of S/W front end Functional Testing and Back end Functional Testing,

Testing team will concentrate on Non-Functional Testing.

Once after developed the application/ready made available only we are supposed to perform Non-
Functional testing

Non-Functional Testing means Characteristics of Software. Apart from Behavior of Application anything
we can do the this testing.

1.Usability Testing:-

In this type of testing one will check the each and every screen of the s/w by following Factors.

1.Easy to use

2.Look and Feel

3.User Friendliness

4.Short Navigations

2.Compatabilty Testing:----System Admins

In this type of testing one will check the application is suitable with different
environments/Browsers/Operating Systems..
a)Hard Ware Compatibility Testing:-

In this type of testing one will check the different Hardware Configurations, Here different
Configurations means Printer, Scanner, Mouse, Keyboard, Camera etc..

b)Soft Ware Compatibility Testing:-

In this type of testing one will check the application is suitable with different softwares or not.

Operating Systems:-

Desktop Operating Systems:-Windows XP2000,Windows 7,Windows 8,Windows 10,Window 11

,7,19 and Mac/IOS, Linux/Unix

Mobile OS:---Android, IOS

Browsers:- Chrome,Firefox,Safari,Edge

Incase of web based application all the browsers suitable or not:-

Gmail, Facebook, IRCTC, JNTU, Redbus

Incase of Window based application all the operating systems are compatible or not we can check.

Ms-office, Antivirus, Eclipse, Medical Store Applications—

Product Based Appications:- Microsoft-Windows Xp, Windows 7, Windows 8, Windows 10, Windows 11

Product Based Companies:- MicrosoftTeams,Qualcome, Note Book Qualcom,--Mother boards -LIC---

Different types policies ,----work on Existing Code----Job Security

Service Based Companies:- TCS, Infosys, Wipro ----Work from scratch --- SSC Examinations
Apps>railyways RRB---

Window base applications:- At a time a single user can use the application.

(Anti Virus,Ms-Word,Note pad,Excel,Note Book )-------

Web Applications:- At a time multiple users can use the application –JAVA---IRCTC/.NET---ICICI/PHP---
Facebook

(Skype,gmail,whatsapp,fb,icici,sbi,LIC,Flipkart,):

Window based Languages:- MS-DOS,C,C++,UNIX,LINUX,Shell Script-----CUI Applications-Command User

Interface(Command User Interface)

Web Based Languages-JAVA,.NET,PHP,PYTHON---GUI Applications—(Graphical User Interface)

Browser/Client Side languages:- Req

HTML:-.html or htm Client/Browser Server

JavaScript:-.jsp.js Response

Angular JS:-.js

Server Side Languages:-

.net/C# Language:- .aspx and asp

Java language:-.jsp,.jsf

PHP language:-.php

Search Engines:-Google,Bingo,Yahooo,MSN

Browser Applications:-Google Chrome,Internet Explorer,Firefox,Safari,Edge

Operating Systems:-Windows XP,Linux,Unix,IOS,MAC

Manual Testing+Automation

Maual+API Testing

Manual +ETL Testing

Operating System—C, C++

Gmail Application:-amazon Application---- Application Performance

Java language---.jsp---10 yrs---1000 lines of code 100 Resources---100 Desktops -Salaries—Java secured

C# .Net language---.aspx—5 yrs---500—lines of code 50 Resources—ICICI –Client-------IRCTC Website

PHP language-----.php—3 yrs—300-- lines of code—30 Resources ---Facebook

Python----.p---2yrs-100 lines--------Data science and Artificial Intelligence—Light weight program—You

tube
IDE's(Integrated Developement Editors/Environments)

English language:-Notepad

Java language :-Eclipse Editor

.Net language:-Visual Studio

3.Installation Testing:-

In this type of testing one will follow the Installation guidelines & install the application in order to
confirm weather the guidelines are suitable for installing applications into the different environments or
not.

Eg:-Testing the Installation Procedure

Manual Testing,Oops{Java},Selenium

4.Performance Testing:-

In this Testing, one will give the request to the server in order to find the Response Time.

Response page time 2Sec< Request URL making time 5 Sec---Performance is High

10Sec< 5 Sec---Performance is Low

1 sec< 2 sec-----High Performance

If Response Time is Less than < Our Expected time then Performance will be High otherwise Low
Performance

Client /Browser Server

Request

Response Amazon

1.Load Testing

2.Stress Testing
1.Load Testing:-

In this type of testing one will give the initially some load and gradually increases upto the Target Load.
In order to check performance we will do this testing.----Load Runner, JMETER ,Web Load Tools

If an application is having ----10 Req’s amazon server

1 Req…2 Req….3 ……..100th Req’s –Target Load of AWS—

Stress Testing:-

In this type of testing, one will give the load greater than Target in order to check the performance.

Target load is 100 Requests—110 Rer’s….120 Req’s…150 Flipkart Server

Security Testing:- Infra Team--

In this type of testing ,one will check whether the application is “Properly Protected” or not .

a)Authentication Testing:

In this type of testing, one will enter different combination of user names and passwords and check
whether only the authorized people are able to access Application or not.

b)Direct URL Testing:-

In this tpe of testing, one will directly entered the URL of secured pages, In order to check whether the
secured pages are directly access or not without login to the application.

c)User Previlege Testing/Firewall Leakage Testing:

In this type of Testing one will enter into the application as a one level of user and will try to access the
user limits in order to check whether the firewalls are working properly or not.

MultiLanguage Testing:-

In this testing, one will conduct 2 ways of testing such as Globalization Testing and Localization Testing
of our Application by entering the multiple people language characters as input.

BFS Domain---Banking Applications-----SBI,ICICI,bankOfAmerica---Product Based Company

Insurance---LIC

Healthcare--NIC Pharma,Glenko Pharma,Jhonson and jhonson

Ecommerce--Amazon,Snapdeal,Flipkart

Travel Domain--Airindia,Makemytrip----
Entertainment-You tube,FB,Whatsapp------

Functional Testings:-
In this type of testing one will performing some testing on Behavior of the
application.
1.Input Domain Testing:-

In this type of testing one will enter size of input data and type of input data through out the screens of
the s/w and observe weather application is working as per client expected manner or not.

2.Out put Domain Testing:-

In this type of testing one will enter valid input data throughout the screens of the s/w and observe our
expected output is coming or not in Databases—Oracle, SQL Server, MongoDB ,My SQL etc…

Select * from employee;

Employee
Empnam Emp
S.No Emp ID e salary Emp DOJ
20-12-
1 1234 Chandu 50000 2014
20-12-
2 1234 Chandu 50000 2014

Select * from Passengerdetails:

Select * from FlightDetails;

Duration Dates Direct Standar Your Room Your Price Total

s Flights d Seats accommodatio & Extras breakdow Price
n Board n
13:00 22/09/202 Charte 247580 Business class Resor TUI Care 123325 445435
3 d t foundatio 4
Flights n
14:00 22/09/202 Charte 247580 Business class Resor TUI Care 123325 445435
3 d t foundatio 4
Flights n

Select * from PassengerDetails; --ORACLE DB/SQL SERVER DB

Tilte Firstname Surname DOB Country Address Mobile Email Info

Mr. Pradeep Teja 247580 India AP 34475874 Fnj Nrjlgn
Mss Pradeep Teja 247582 India AP 34475874 Fnj Nrjlgn

Database Commands:-

Select,alter,drop,truncate—DDL cmds

Select * from employee;

Select * from passengerdetails page;

Insert,Update,delete DML Cmds---CRUD operations

Savepoint,Commit,Rollback—TCL cmds

3.Error Handling Tesitng:-

In this type of testing one will enter valid input data through out the screens of the s/w and observe our
expected Error message is coming or not.

--Developer Error Message-- Oops, this field does not accept numbers or certain special characters.

Actual Result:- Made by Developer

This field does not accept first names longer than 32 characters. Please give us a call if your
first name is longer than allowed by the field.
Expected Result:- Made by Client-Product Owner/BA

This field allows Max 32 chars only.

If (Actual result !== Expected Result) then we have to raise a Defect to Dev team.

If (Actual result == Expected Result) then we have to pass the Test case.

How to Log a Defect:-

Defect Summary/title:- Invalid Error message has been shown for First name text field.

Priority:- P1,P2,P3,P4—P1-Hight Priority&P2-Medium Priority&P3-Low Priority

Seviority:-S1,S2,S3,S4—S1 -High Seviority&S2-Medium Seviority & S3-Low Seviority

Defect Description:

Steps to be Reproduced:-

1.Launch the TUI web application.

2.Initiated some search in search panel

3.Navigate till Passenger details page.

4.Provide some invalid text in First name field and click on tab

Observed that Invalid Error message has been shown.

Actual Result:- The response that we receive from the application is called Actual result.

This field does not accept first names longer than 32 characters. Please give us a call if your
first name is longer than allowed by the field.
Expected Result:- What client wants to display the result on the application.

This field allows maximum 10 chars only.

Actual Result:- What applications shows
The email address you entered isn't connected to an account. Find your account and
log in.

Expected Result:- What client is expecting on app.

You have entered invalid email

Actual Result:-

Use between 2 and 50 letters. No numbers or special

characters.
Expected Result:-

First name field allows only characters

Incident:- You have to inform to Environment support team/Devops team when we encounter
application blockers/Network Errors with some status codes

Defect:- It’s relevant to Functionality of an application.

If (Actual result !== Expected Result) then we have to raise a Defect to Dev team.

How to raise/Log a Defect to a developer?

Defect Summary/Title:- Invalid Error message has been displayed for the First name field.
P1-High,P2-Medium,P3-Low
S1-High ,S2-Medium,S3-Low,Cosmetice issue
Priority:P1-Medium
Severity:S2-Medium
Defect Description:
Steps to be reproduced:-
1.Launch the TUI application. https://www.tui.se/se/hitta-resa/checkout
2.Initiate some search in search panel.
3.Navigate till checkout page.
4.Enter invalid maximum characters in First name field
Observed that Invalid Error message has been displayed for the First name field.
Actual result:-
This field does not accept first names longer than 32 characters. Please give us a call if your
first name is longer than allowed by the field.

Attach the evidences---

Expected Result:-
This field allows maximum 10 chars only.
If(Actual result==Expected result) =PASS
If(Actual result!==Expected result) =FAIL we need to log a Defect/Issue
We need to compare both the things
1.Client requirements  Developed Application
Bcz the Developed application should meet Client requirement
Developer has to develop the application as per Client Requirements only.
Testers have to test the application as per Client Requirements only.

Client Expected Error message:-

Please enter a valid First name with proper text—When uset comits a mistake

Invalid Error message:-

Actual Result:- Oops, this field does not accept numbers or certain special characters.—Actual
Result
Expected Result:- Numbers should not be entered.
Valid Error Message:- Numericals are not allowed---Client Requirement –Expected result

Developer can comit some code error or configurations errors

Actual displayed Error message:- Please enter a valid First and Middle name

When Client Expected result(Client Requirement)=! Actual Result(Application response)-----WE should

log a Defect

Client Error Message—The Entered data is not valid, Please provide the text data only/

If any mismatch occurs between Application result and Client expected Result then we can log a
defect/bug

Expected Result:-

First name field should allow only Characters---It was given by the Client

Actual Result:-- Oops, this field does not accept numbers or certain special characters.
Wrong password. Try again or click Forgot password to reset it.

Oops, this field does not accept numbers or certain special characters.--- It was given by the
Developer

prashhanth07@gmail
Client Expected Result: -What Client is expecting to be displayed on webpage
“Provide String Valid Charatcters ”

Actual Condition (!=)Expected condition----WE can log a defect to Dev team

Actual Condition (=)Expected condition----WE can Pass the Test case --

Dev team has implemented the below Error message:-

Oops, this field does not accept numbers or certain special characters.
Client Expected Result is:-Only Text data should be allowed

Actual Result:- Oops, this field does not accept numbers or certain special characters.—Dev
team
Client Expected Result is:- Only Text data should be allowed

Log a Defect:-
Developer:-
Oops, this field does not accept numbers or certain special characters.—Actual Result
Client has given one requirement:-
First Name field should allow only text data---Expected Result
When (Actual Result !== Expected Result)--FAIL
When (Actual Result == Expected Result)--PASS
E should log a Defect to Dev Team.

How to Log a Defect:-

1. Defect Summary/Defect Title:- Invalid Error message has been displayed for First name field

2.Priority:- P1-High ,P2 -Medium,P3-Low

High P1:- Defect should be fixed on demand based/Immediately Dev team has to respond and provide
the fix for the defect.

3.Seviority:-S1-High,S2-Medium,S3-Low

High Seviority:- Testers need to log an incident to Devops team/Environment Support team.
Hight Priorot& High Seviority:-

1.Defect Title/Summary:- Invalid Error message has been displayed for First Name field.

Seniority:-S1.S2,S3,S4----S1 -High S2—Medium S3—LOW S4---Cosmetic Issue

Priority:- P1,P2,P3,P4---P1 –High P2—Medium P3---Low---P4—can be ignored

If the issue is belongs to functionality of application then we should assign it to Developers

If the issue is belongs to some Network /Server issue of then we should assign it to Devops Team
https://dev.tui.co.uk/----DEV Environment

https://sit.tui.co.uk/-----SIT Environment

https://uat.tui.co.uk/-----UAT Environment

https://www.tui.co.uk/----->Live Environment

4.Defect Description:-

Steps to be Reproduced:-

1.Log into the application.

2.Initiate some search in search panel ---given Departure Airports & Given passengers

3.Navigated to Search results page

3.navigate till Passenger details page

4.Observed that First name field is not prompted with a valid error message

Actual result:- Firstname field is not prompted with an valid error message

Oops, this field does not accept numbers or certain special characters.

Expected Result:-Valid Error message should be displayed.

Numericals are not allowed

5.Attach some evidnces:-

6.Assign this defect to right Developer or Asignee name

Steps to be Reproduced:-

1.Log into the Makemy trip application

2.Inisitate some search in search panel

3.navigated till passenger Details page

Actual Result:-Observed that Invalid Error message has been displayed--- Please enter a valid First and Middle
name
Expected Result:- Valid Error message should be displayed.-Please enter a valid First name with proper text

Attach the Evidences----

Assign to one Developer

Defect Summary:- Invalid Error message has been displayed in Surname field.

Priority:- High,Medium,Low,Cosmetic---Finalized by BA/Dev

Seviority:- High,Medium,Low,Cosmetic---Finalized by Testing team

Root cause Analysis:- Code/Functionality Issue, Env Issue, Data Issue, Network Issue, Design Issue

Description:-

Steps to be Reproduced:-

1.Login to the TuI Application.

2.Initiate search in search panel page.

3.Navigate till passenger details page

Attachments:- Evidences

Asignee:-Developers

Submit---

4.Actual Result:-Observed that Invalid Error message “Oops, this field does not accept numbers or
certain special characters.” has been displayed in Surname field.

Expected result:- valid Error message “The Entered data is not valid, Please provide the Numberical data
only” should be displayed.

Test management Tools/Defect Tracking Tool—To perform STLC activities…

JIRA,BUGZILLA,Qtest and Ralley

4.DataBase Testing:-

In this type of testing one will perform actions on the application screen and observe the impact is
coming in internal database or not.

JAVA People Will Use ORACLE Database

.Net People Will Use –SQL SERVER Database

PHP Paople Will use—My Sql Database

Python People Will—MongoDB

DDL Commands:-Select,Drop,Alter,Truncate---

Select *from passenger details page;

DML:-Insert,update,delete

DCL:Commit,Rollback,Savepoint

SSRR---Smoke Testing ,Sanity Testing ,Retesting and Regression Testing

5.SMOKE Testing:- 50 TC’s

Smoke testing/End To End Testing/Happy Flow path
Amazon:- ----End to end testing ----Smoke testing----- Order ID
MakeMytrip-----End to end testing-----Smoke testing----Booking reference ID
Bank of America--- End to end testing-----Smoke testing----Customer A/c

To test Promotions&Coupons----Sanity
Cart functionality---Sanity
Smoke Testing is done to make sure if the build we received from the development team is
testable/Stable or not.---End to End testing---If the End to End testing is passed without any blockers
then we can declare that Smoke test is done.

TO check the stability of the freshly released build, we have to perform Smoke Testing

It will be done before releasing the build to the testing department , the developer will check whether
the build is proper or not that is known as SMOKE Testing

Page Blocker-page not found-501 Bad gate way/Server not found -500 Error is something which is
blocking the navigation flow /End to end flow---We need to log an incident to Devops team
An issue/Defect is something which is failing particular functionality on a page and not effecting the
navigation flow of the application.

To make sure that given build is properly working or not ,we perform Smoke testing…..

Or To make sure that build is stable

1.Weather the build is properly installed or not.

Smoke Testing will be performed for End to End testing---

Banking application:-Customer ID---Resultant

LIC Application:-One Policy ID

Amazon application:-Order ID

Entertainment application:-FB Account

IRCTC---Train ticket

6.SANITY Testing/ --BlackBox Testing—SIT System Integration Testing—500 TC’s

In order to confirm whether it is proper conducting detail testing or not.

Usually during this type of testing they will check following cases.

As part of sanity we will need to make sure that each independent functionality is working fine or not.

2.weather one can navigate to all the pages of application or not.--- Error Message shown like --Page
Not Found!!- Environment Support Team (EST) Will Take care of those issues and As a Tester, We need
to Log an Incident to EnvironmentSupport Team/ Devops Team

3.weather all the important functionality are available or not.

4.weather all the required connections are properly established or not.

Re testing:-
Retesting is to perform the check the given fix is properly working or not.
TO check the defect is properly fixed or not, we perform Retesting
In this type of testing one will test the same functionality again and again by entering the different set
of data in order to check weather it is working as per client expected manner or not.
 Defect functionalities are really rectified or not they will test.

TO test the application weather the Defect is Really Rectified or Not

GMAIL Login Page:- Min pwd range-6 characters, Max 8 chars

Username

Password Testing

Login

Defects

Developer

Username

Password

Login

Regression Testing:-/Automation
Regression Testing is used to make sure that new code changes should not have side effects on the
existing functionalities.

It is a type of testing in which one will perform testing on the already tested functionality again and
again. This type of testing we can call as a Regression Testing.

Functional Test Suite:- 100 Requirements/User stories--1100 Testcases—End to End Testing—110 REq

Automated Scripts will be prepared for End to End Testing Or Smoke Testing –30 to 40 Scripts

Regression Test Suite:- 10 Req’s---5 New Req’s +5 Old Req’s --10 scripts—5 Re

1000 TC’s -----TestLead will decide How many TC’s are need to be tested Manually and Hoe many TC’s
are need to be Automated

Windows XP Version 1…….Windows 7,8,10 Now Windows 11

MS-word/Notepad Ms-Excel MS-Teams Office 365

Usually we do Regression testing in 2 scenarios

1.whenever the testers identify the defects then raise those defects to the developers,

next build is released then the test engineer will check Defect functionality area as well as related
functionality /Surrounding Functionality once again.

1.We need to make sure that the defect functionality area is working fine

2.whenever some new features are added to the existing functionalities then next build is released to
the Testing team the test engineer will check all the related older features along with newly added
features once again.

This type of testing is known as “regression Testing”.

Note:-

Regression testing starts from second build and continuous upto the last build

Testing the New features for the 1st time is known as New Testing/Sanity Testing.

It is not Regression Testing.

Test Suite is nothing but Collection of Testcases…

SIT Suite ---SANITY Testing-----Functional Testing(1000 Manual Testcases)--100 Automation Testscripts

(20 Features)----850 Manual test cases left—70 Automation scripts for Sanity

Smoke testing/E2E Suite --- --100 TC’s for Manual testing & pulled 10 Automation Test scripts

Regression Suite---- 200 Manual Test cases (50 TC’s (TC’s with more defects(5 Automation scripts)) + 50
TC’s (Newly added features(10 automated scripts))+10 Automation Automations Test --

100 Manual TC’s to perform regression

15 Automation scripts to perform Regression

UAT Suite---(100 Manual TC’s +20 Automation Scripts) Alpha & Beta….(SIT + Regression Test cases)

Microsoft:--

Windows XP—1990--- Ms-Office—Ms-Word,Ms-Excel,Ms-Power point

Windows 7—2000------Ms-Teams,Notebook
Windows 8, --- Ms-Outlook— Own product of Microsoft which we can use it in real time organizations

Windows 10---Ms-One Drive—TO backup the data into CLoud

Windows 11----Office 365--- Ms-Word,Ms-Excel,Ms-Power point, Ms-Teams,Notebook

Windows 7—2010----50 features—ms-word,Poerpoint,Notepad---100 Automated Test Scripts—1000

Manual Testcases

Windows 10—2020---Newly 10 features—Office 365---MS-Teams, Notebook—10 Test scripts—100

Manual test cases ---

Regression Suite-20 Automation TC’s---Which covers End to end Testing+ Newly 10 features

100 Manual Testcases+1000 manual Testcases(1100 TEstcases)—manually

Instead of executing all the 1100 Manual scripts,we can run only 60 scripts….

Test Suite is a Collection of Test Cases:

SIT Suite----System Integration Testing---1100 Test Cases---60 Automation scripts

Regression Suite—End to end TC’s--10 scripts---Newly added TC’s ---100 TC’s

10 scripts---WE have to pick the testcases randomly which are really effected by the risen defects and
newly added features

UAT Suite-----(User Acceptance Testing)These scripts should cover all the functionalities

What is an Adhoc Testing?-

Adhoc Testing simultaneous Test design and Execution.
Adhoc testers dive into the application without having pre defined Test cases and mainly
execute application depends on

LIC -----5 years---Different Policies

SBI LifeInsurance----
ICICI Prudential Life Insurance
  Creativity
 Knowledge
 Passion to conduct Testing
 Experience or Memory of past events

During Adhoc Testing more freedom will be given to the tester.

Scenario 1: We are working for Major Banking Domain client, the Application which we are
supposed to test is very critical to the client Business/Complex Application for this scenario
SBI s/w Testers can work with ICICI s/w
Scenario 2: A tester is working in the same project from last 5yrs; he gained more knowledge on
Domain/Business flow, Critical areas of the app, frequently failed functions….

Design the High Level Scenarios and Low Level Scenarios---Testers

------BRS---Test Case Design-Testers
------Test Case Execution-Testers---Defects---
Reports--Tools
Test Strategy-Project Lead
Test Plan Document ---Test Lead
Requirement analysis-----Testing Team
Design High level scenarios(Test Scenarios)--Low level Scenarios(test cases)
Peer Review should be done among the QA team---Once Peer review is done, BA team will
move the status to Ready for Test
Executing the designed Test cases--While executing the TC’s, we encounter few
issues/Defects
We need to raise a defect/Bug to Developers
Developers will provide Fix for the raised defects
WE have to perform Retesting for the fixed defects to make sure whether the defects are
properly fixed or not.
What are the advantageous of Adhoc Testing?
1. Testers will be given with the complete freedom, so tester apply their creativity and
experience
2. Quick finding defects is possible in adhoc Testing
3. Some times Test cases may not cover all functionalities then adhoc Testing helps to find
defects which are not covered by test cases.
4. No need to spend time on documentation—Testcases/Requirements
5. Test to break attitude

What are the Drawbacks of Adhoc Testing?

1. No systematic approach—They won’t follow any pre designed Test cases
2. No guarantee on what we have tested and how we have tested
3. No reusability
4. No Verification in adhoc Testing

What is Formal Testing ?

Formal Testing mainly focus on Testing of an application based on Pre defined process (BRS),
Pre designed Test cases.

Formal Test Approach:STLC:-

 Testable requirements will be given to tester—Requirement analysis

 Design High level scenarios(Test Scenarios)---Low level scenarios (Test cases, Test
Script)
 Testing team do review of the Test cases---Peer Review—
 Comments :-Test Ok---New---In progress—Ready to Test—BA Approved
 Status:-Ready for Test Execution---While we are executing the testcases we can
encounter some defects then immediately we are supposed to log some defects..
  Once code is ready for Testing involve in execution of the software based on pre defined
Test cases to find defects in Application

JIRA &HP ALM and Bugzilla and Qtest –Test Management Tools/Defect Tracking Tool