KEMBAR78
Manual Testing tutorials and Interview Questions.pptx
Brickred Systems
SDLC
What is
Software
Testing?
Software Testing is a
method to check
whether the actual
software product
matches expected
requirements and to
ensure that software
product
STLC
Functional
Testing
Unit
Integration
System Testing
Interface Testing
Regression
UAT
Non-Functional
Testing
• Documentation Testing
• Installation / Uninstallation
• Performance testing (Load,
Stress, Spike, etc.)
• Reliability
• Security
Types of Software Testing
• Accessibility testing
• Acceptance testing
• Black box testing
• End to end testing
• Functional
• Non-functional testing
• Interactive testing
• Integration testing
• Load testing
• Performance testing
• Regression testing
• Sanity testing
• Security testing
• Smoke testing
• Stress testing
• Unit testing
• White-box testing
Accessibilitytesting
Accessibility testing is the practice of making your
web and mobile apps usable to as many people as
possible.
Acceptance testing
Acceptance testing is a quality assurance (QA)
process that determines to what degree an
application meets end users' approval.
Black Box testing
Black box testing involves testing a system with no
prior knowledge of its internal workings. A tester
provides an input, and observes the output
generated by the system under test.
End to Endtesting
End to End Testing is usually executed after
functional and System Testing. It uses actual
production like data and test environment to
simulate real-time settings.
Functional testing
Functional testing is a type of testing that seeks to
establish whether each application feature works as per
the software requirements.
Each function is compared to the corresponding
requirement to ascertain whether its output is
consistent with the end user's expectations.
Non-Functional testing
NON-FUNCTIONAL TESTING is defined as a type of
Software testing to check non-functional aspects
(performance, usability, reliability, etc) of a software
application.
Interactivetesting
Interactive testing enables testers to create and
facilitate manual tests for those who do not use
automation and collect results from external tests.
Integrationtesting
This is a type of software testing in which the different
units, modules or components of a software application are
tested as a combined entity.
Note: Different modules are coded by different developers.
Loadtesting
Load testing is a kind of performance testing which
determines a system's performance under real-life load
conditions.
Performance testing
Performance testing is the practice of evaluating how a system
performs in terms of responsiveness and stability under a
particular workload.
Performance tests are typically executed to examine speed,
robustness, reliability, and application size
Regressiontesting
Performance testing is the practice of evaluating how a system
performs in terms of responsiveness and stability under a
particular workload.
Performance tests are typically executed to examine speed,
robustness, reliability, and application size
Sanitytesting
Performance testing is the practice of evaluating how a system
performs in terms of responsiveness and stability under a
particular workload.
Performance tests are typically executed to examine speed,
robustness, reliability, and application size
Securitytesting
Performance testing is the practice of evaluating how a system
performs in terms of responsiveness and stability under a
particular workload.
Performance tests are typically executed to examine speed,
robustness, reliability, and application size
Smoketesting
Performance testing is the practice of evaluating how a system
performs in terms of responsiveness and stability under a
particular workload.
Performance tests are typically executed to examine speed,
robustness, reliability, and application size
Stress testing
Performance testing is the practice of evaluating how a system
performs in terms of responsiveness and stability under a
particular workload.
Performance tests are typically executed to examine speed,
robustness, reliability, and application size
Unit testing
Unit testing is a software development process in
which the smallest testable parts of an application,
called units, are individually and independently
scrutinized for proper operation.
White box testing :
It is also known as clear box testing, happens when
you have insight into the code and/or general
knowledge about the architecture of the software
in question
Alpha testing
This is done by testers and quality analysts
inside the organization.
Exploratory Testing:
You learn and test the software
simultaneously
Monkey testing:
Performing random testing without any plan
with
Ad-hoc testing:
Performing random testing without any plan
Beta testing
This is done by real users who will be actually
using the software.
Compatibility Testing
A compatibility test is an assessment used to
ensure a software application is properly working
across different browsers, databases, operating
systems (OS), mobile devices, networks and
hardware.
Priority
• P0 — This is a major blocker. Put down everything and tackle it.
• P1 — Must be tackled on next available time/resources
• P2 — Should be tackled but not urgent
• P3 — Will be good to get it done if no other priority
• P4 — Can be done at some future release.
Severity
Blocker
Critical
Major
Medium
Low
Pesticide
Paradox
Pesticide Paradox principle says that
if the same set of test cases are
executed again and again over the
period of time then these set of
tests are not capable enough to
identify new defects in the system
Root Cause
Analysis
(RCA)
RCA is a technique used to find answers as to
why a problem has happened in the software.
Project
Management
• Agile
• Scrum
Agile Methodology
Agile is an iterative approach to project management and
software development that helps teams deliver value to
their customers faster and with fewer headaches.
Instead of betting everything on a "big bang" launch, an
agile team delivers work in small, but consumable,
increments.
What is Scrum?
Scrum is a framework for project
management that emphasizes teamwork,
accountability and iterative progress toward
a well-defined goal.
Scrum
ceremonies
• Sprint Planning
• Daily Scrum
• Sprint Review
• Sprint Retrospective
Mobile Application Testing
FUNCTIONAL
TESTING
INTERRUPTION
TESTING
LOCALIZATION
TESTING
SPEED TESTING MEMORY LEAK
TESTING
USABILITY
TESTING
PERFORMANCE
TESTING
Functional Testing
• App installs and launches correctly
• Users can sign-up and log into the app easily
• Text boxes, buttons, menus, and icons function accurately
• Push notifications render correctly and appear at the right intervals -
Deep linking -
• Any transactions or purchases should happen seamlessly
Interruption Testing
• Incoming or phone call when an application is running
• Incoming message or SMS when an application is running
• Low battery when an application is running
• The device is plugged in or out of charging when an application is
running
• Device shutting down when an application is running
• OS upgrade occurring when an application is running
• Loss and restoration of the network while an application is running.
Localization Testing
• Pricing Currency
• Language
• Access
Speed Testing
Memory Leak Testing
• A memory leak refers to a situation in which the app fails to return
the memory it has acquired for temporary use in order to function
Usability Testing
• Smooth, visually appealing layout and design
• A high degree of intuitiveness
• Quick response time – Most users prefer apps that launch within 2-3
seconds after tapping the icon.
Performance Testing
• Device performance: Installation and log-in time, battery
consumption, memory consumption, etc.
• Network performance: Delays, errors, pauses in receiving digital
information or rendering network-activated features
• API/Server performance: Speed and formation of data transfer from
back-end to front-end
• Recovery capabilities: Built-in back-up and recovery functions that
can save or recover user data in the event of data loss.
Interview
Questions
What is difference between
test Plan, test Scenario and test
Cases?
What are the responsibilities of
Scrum Master ?
What are the reports you
prepare during Sprint ?
What are the columns you will
include while writing test
cases?
What is difference between
Priority and Severity?
Give me Examples.
What is the First Status of bug
when user created on Jira?

Manual Testing tutorials and Interview Questions.pptx

  • 1.
  • 2.
  • 3.
    What is Software Testing? Software Testingis a method to check whether the actual software product matches expected requirements and to ensure that software product
  • 4.
  • 5.
  • 6.
    Non-Functional Testing • Documentation Testing •Installation / Uninstallation • Performance testing (Load, Stress, Spike, etc.) • Reliability • Security
  • 7.
    Types of SoftwareTesting • Accessibility testing • Acceptance testing • Black box testing • End to end testing • Functional • Non-functional testing • Interactive testing • Integration testing • Load testing • Performance testing • Regression testing • Sanity testing • Security testing • Smoke testing • Stress testing • Unit testing • White-box testing
  • 8.
    Accessibilitytesting Accessibility testing isthe practice of making your web and mobile apps usable to as many people as possible.
  • 9.
    Acceptance testing Acceptance testingis a quality assurance (QA) process that determines to what degree an application meets end users' approval.
  • 10.
    Black Box testing Blackbox testing involves testing a system with no prior knowledge of its internal workings. A tester provides an input, and observes the output generated by the system under test.
  • 11.
    End to Endtesting Endto End Testing is usually executed after functional and System Testing. It uses actual production like data and test environment to simulate real-time settings.
  • 12.
    Functional testing Functional testingis a type of testing that seeks to establish whether each application feature works as per the software requirements. Each function is compared to the corresponding requirement to ascertain whether its output is consistent with the end user's expectations.
  • 13.
    Non-Functional testing NON-FUNCTIONAL TESTINGis defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application.
  • 14.
    Interactivetesting Interactive testing enablestesters to create and facilitate manual tests for those who do not use automation and collect results from external tests.
  • 15.
    Integrationtesting This is atype of software testing in which the different units, modules or components of a software application are tested as a combined entity. Note: Different modules are coded by different developers.
  • 16.
    Loadtesting Load testing isa kind of performance testing which determines a system's performance under real-life load conditions.
  • 17.
    Performance testing Performance testingis the practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size
  • 18.
    Regressiontesting Performance testing isthe practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size
  • 19.
    Sanitytesting Performance testing isthe practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size
  • 20.
    Securitytesting Performance testing isthe practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size
  • 21.
    Smoketesting Performance testing isthe practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size
  • 22.
    Stress testing Performance testingis the practice of evaluating how a system performs in terms of responsiveness and stability under a particular workload. Performance tests are typically executed to examine speed, robustness, reliability, and application size
  • 23.
    Unit testing Unit testingis a software development process in which the smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation.
  • 24.
    White box testing: It is also known as clear box testing, happens when you have insight into the code and/or general knowledge about the architecture of the software in question
  • 25.
    Alpha testing This isdone by testers and quality analysts inside the organization.
  • 26.
    Exploratory Testing: You learnand test the software simultaneously
  • 27.
    Monkey testing: Performing randomtesting without any plan with
  • 28.
    Ad-hoc testing: Performing randomtesting without any plan
  • 29.
    Beta testing This isdone by real users who will be actually using the software.
  • 30.
    Compatibility Testing A compatibilitytest is an assessment used to ensure a software application is properly working across different browsers, databases, operating systems (OS), mobile devices, networks and hardware.
  • 31.
    Priority • P0 —This is a major blocker. Put down everything and tackle it. • P1 — Must be tackled on next available time/resources • P2 — Should be tackled but not urgent • P3 — Will be good to get it done if no other priority • P4 — Can be done at some future release.
  • 32.
  • 33.
    Pesticide Paradox Pesticide Paradox principlesays that if the same set of test cases are executed again and again over the period of time then these set of tests are not capable enough to identify new defects in the system
  • 34.
    Root Cause Analysis (RCA) RCA isa technique used to find answers as to why a problem has happened in the software.
  • 35.
  • 36.
    Agile Methodology Agile isan iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches. Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments.
  • 37.
    What is Scrum? Scrumis a framework for project management that emphasizes teamwork, accountability and iterative progress toward a well-defined goal.
  • 38.
    Scrum ceremonies • Sprint Planning •Daily Scrum • Sprint Review • Sprint Retrospective
  • 39.
    Mobile Application Testing FUNCTIONAL TESTING INTERRUPTION TESTING LOCALIZATION TESTING SPEEDTESTING MEMORY LEAK TESTING USABILITY TESTING PERFORMANCE TESTING
  • 40.
    Functional Testing • Appinstalls and launches correctly • Users can sign-up and log into the app easily • Text boxes, buttons, menus, and icons function accurately • Push notifications render correctly and appear at the right intervals - Deep linking - • Any transactions or purchases should happen seamlessly
  • 41.
    Interruption Testing • Incomingor phone call when an application is running • Incoming message or SMS when an application is running • Low battery when an application is running • The device is plugged in or out of charging when an application is running • Device shutting down when an application is running • OS upgrade occurring when an application is running • Loss and restoration of the network while an application is running.
  • 42.
    Localization Testing • PricingCurrency • Language • Access
  • 43.
  • 44.
    Memory Leak Testing •A memory leak refers to a situation in which the app fails to return the memory it has acquired for temporary use in order to function
  • 45.
    Usability Testing • Smooth,visually appealing layout and design • A high degree of intuitiveness • Quick response time – Most users prefer apps that launch within 2-3 seconds after tapping the icon.
  • 46.
    Performance Testing • Deviceperformance: Installation and log-in time, battery consumption, memory consumption, etc. • Network performance: Delays, errors, pauses in receiving digital information or rendering network-activated features • API/Server performance: Speed and formation of data transfer from back-end to front-end • Recovery capabilities: Built-in back-up and recovery functions that can save or recover user data in the event of data loss.
  • 47.
  • 48.
    What is differencebetween test Plan, test Scenario and test Cases?
  • 49.
    What are theresponsibilities of Scrum Master ?
  • 50.
    What are thereports you prepare during Sprint ?
  • 51.
    What are thecolumns you will include while writing test cases?
  • 52.
    What is differencebetween Priority and Severity? Give me Examples.
  • 53.
    What is theFirst Status of bug when user created on Jira?