Software : Is a collection of programs

programs : Is a collection of Instructions

0 & 1

Types of S/w

>> System S/w : OS

public & Private

--Windows : 32/64bit , XP , Vista , 2003 , 7 , 8.1 , 10(12), 11

--Mac : intel/arm64 ,
--Linux/Unix

>> Programming S/w : Compiler/Debugger (CMD)

>> Application S/w : Web Application . Mobile Application & Desktop Application

S/w Testing: Is an activity to detect & Identify the defects in a s/w

Error : Human /Machine made mistake

Defect : An issue found by testing team but yet to be accepted by Dev team
Bugs : Deviation of Actual output
Failure : Once Delivered to Customer & its not working properly

Is S/w testing worth

How much salary can i can accept : 3.5lpa - 35lpa
where to start

what are the factors that decide the quality of a s/w

Bug free(99%)
On time Delivery
Within Budget (10Lakhs - 2.5Lakhs)
Meets Customer expectations

Why the s/w has bugs ?

--Complexity
--Communication (No / Miss)
--Programming errors
-- Frequent change of requirement
-- Lack of skilled testers

product : Market requirements (Meta , Amazon , HP)

Project : Specific Client requirement (TCS , Infosys , Accenture )

P1 : Manual
P2 : Manual + API
P3 : Manual + API + Database

Project 1 : Manual (p3)

Project 2 : Manual + API (p3)
Project 3 : Manual + API + Database (p3)
Role & Designation

Team Members

Project Team : Project Manager /Project Cord

Business team : BA /PO
Architect Team : S/w , N/w
Development team : Developers
Design Team : UX-UI
Testers :
Devops team : Devops engineer
Database team : DBA , DBE
Technical Team :

Tier 1 : MNC
Tier 2 :
Tier 3 :

Domains (Area of Expertise)

Insurance
Finance
Banking
E Commerce
Aerospace
Automotive

SDLC (Software Development Life Cycle )

Water Fall Model (One Time Approach Model) Winston W Royce - 1970

Adv : Quality of the project /Finding bugs will be less

Disad : Requirements changes are not allowed/Testing is done after development

Spiral Model (Version Control Model ) Barry Boehm - 1986

Adv : Requirement changes are allowed after each cycle is completed/ Testing is
done in each cycle
disad : Requirement changes are not allowed in between the cycle / Smaller projects

V&V Model (Verification & Validation)

Black Box Testing (Testers)

Acceptance Testing :is a form of testing in which it can be carried in any forms by
any person to validate is that fine or not
-UAT Testing (User Acceptance Testing ) :

System Testing
-GUI Testing : Graphical user interface (
Checkboxes , Dropdown , buttons , radio buttons , colors , images , tool tips
, mouse hover
 - Functional Testing : Testing the scope/Behavior of the testing
Database Testing : (add./edit/delete/update)
Cookies (Temp data )
Error Handling (Excepted /Unexpected )

- Non Functional Testing

-- Performance testing : 140cr+ (1.4cr) Loadrunner/Jmeter

-- Security : HTTPS/HTTP (Hyper Text Transfer Protocol + Secured) /
Password

(12-24)/admin/admin123/iloveyou/qwerty@1234/dharmaj@987456321/dharmaj@12022025
1 Number/1 UC / 1LC/1 SC / 28-90
URL (Uniform resource locator )

-- Recovery : MFA
-- Configuration/Installation (EULA Screen - End user license agreement
)

- Usability Testing :

White BoX testing (Developers )

Unit Testing/Component Testing : Testing single unit/component is known as

Integration Testing : Testing multiple units at atime & making sure that the
functionality is working fine

Static Testing Techniques

Review :
BRS (Business Requirement specification)
FRS/SRS (System Requirement Specification)
Test Plan
Test Scenario
Test Cases
Defects/Bug Reports
RTM(Requirement Tractability Matrix)
Codes/Code Analysis
DSR/WSR (Daily Status Report/Weekly Status Report)
Automation Feasibility Study
Test Closure Document

Walkthrough :
Inspection :

Adv : Requirement changes are allowed at any phase of development/Testing is done

in every phase
Disad : Initial Investment is more / Too Much of Documentation
Agile Model(Ken Schwaber & Jeff Sutherland)- 2001 :

Iterative & Increment Model

adv : Easy to adopt / Communication is at its best / Customer fav

disad : Less Documentation / It is not suitable for bigger

Scrum Framework(Set of rules)

scrum : its a method use to implement agile methodlogy , in which the time is been
divided into sprints & completion of them

sprint : a work alloted for the dev team (dev + test ) & completion of them

sprint max : 1 month

sprint min : 1 week
cust

Agile Roles

Product Owner : Make sure that roadmap of the project is been taken care +
Responsible for project delivery

Exp : 6+ years

Scrum Master : Is responsible to make sure the team is achieving the set target
/Organ scrum call

10+ Years (CSM - Scrum Alliance)

Development team (Dev + Testers )

Stake Holder

Agile Ceremonies

Sprint Planning
when : at the beginning of the project
who : PO + SM + DEV
what(duration) : 1hr- 2hr

Daily Stand up
when : daily/bi-daily
who : PO+SM+DEV
what(duration) : 15-30mn

Sprint Review/demo
when : at the last of the sprint
who : PO + SM + DEV + SH
what(duration) : 30mn

Retrospective
when : after the sprint review
who : SM + DEV
what(duration) : 15-30mn
User story : Collection of Requirements of a single unit/Module

Story point : Estimation given to complete the set of work

1 story point : 1 day/1 hour : 0,1,1,2,3,5,8,13

Task : Set of work allotted to the any dev/tester/PO

Raw : rough estimation

EPIC : COllection of User story, task & Bugs

1 user story
5-6 task
10 bugs

Agile Artifacts

Sprint Artifact : User story , Bugs , Task , Sprint

Product Artifact : Future sprint , task , user story

Kanban

Types of agile methodology

-Kanban
-scrum
-Extreme Programming(XP)
- Feature Driven Development (FDD)
-Lean
-DSDM (Dynamic Systems Development Method)
-Crystal

Regression Testing : code changes/requirements been added

Unit Regression : Testing only the changes done by dev
Regional Regression : Testing the changes along with the impacted modules
Full Regression : Testing the complete application

Re-Testing : testing the reported bugs

Compatibility Testing : Making sure that the s/w is working fine in any s/w , n/w ,
h/w components
Positive Testing :Testing the application with +ve/true/valid
Negative Testing : testing the application with -ve/invalid/false input
End to end Testing : Testing the complete application from A to z

Informal ways of testing

Exploratory Testing : NO SRS , Time Consuming , NO test cases

Bug can be thought as feature / feature can be thought as bug

Adhoc Testing : No SRS ,when a tester have the knowledge of the application , No
Test cases
Monkey Testing : testing the Application with random inputs to check where the
application is crashing

Gorilla Testing : testing the Module with random inputs to check where the
application is crashing

Smoke vs Sanity Testing

Black Box Vs White Box Testing
Alpha Vs Beta Testing

5 = 2/3/4/5 - 1 (Observation)
check if any existing issue is available

Severity : Impact Ness of the bug

Priority : importance given to fix the bug (P1/p2/p3)

High Severity vs High Priority

Low Severity vs Low Priority
High Priority vs low Severity
Low Priority vs highest severity

Software Testing Principles

Testing shows the presence of defects

Early Testing
Exhaustive testing is impossible
Testing is Context Dependent
Defect Clustering (80% of the bugs can be fixed with 20 %)
B1 , B25, B54, B87
Pesticide Paradox
Absence of error fallacy : if there is a less amount of user interaction then the
detects of the bugs would less which would cause to absence to errors

Test Design Techniques

BVA (Boundary Value Analysis ) : min & max (min-1) (max+1)

ECP (Equivalence class Partition) : (1000) (100..100 ) (2)(5)(1) ,(200)(200)
DTT (Decision Table Testing )
EG (Error Guessing ) :

ankit : 2
archana : 5
Ashwini : 10

Test Scenario

API (Application Programming Interface )Testing

Types

SOAP (Simple Object access protocol ) - 20%

REST (Representational State Transfer ) - 80 %

URL - Uniform resource locator/Indicator

https:// - Schema
demowebshop.tricentis.com - Domains
/login - Path (Endpoints )

HTTPS Request / REST API Methods

GET : Fetch any data - 200

POST : create a new data - 201
PUT : update any existing data - 200
DELETE : Delete an existing data - 204

[email protected]

nodejs
npm

json server
json format

JSON/XML : Java Script Object Notation

HTTPS Status code

200
201
202
204

300/400/500

pre -requesitie
request
reponse

Introduction to selenium (0.000000001%)

Any one lang (Java + Phython + PHp + Ruby + .net + JavaScript + C++ , C)

java + selenium

selenium

- OS/Browsers/Languages
-Open source
-Major Community Support
- Web applications