SQA_Unit 3.pdf it is a database education

Agenda
Performance Testing,
Volume Testing,
Stress and Load Testing,
User Acceptance Testing,
Security Testing,
Usability Testing,
Usability Testing,
Localization Testing,
Documentation Testing,
Regression Testing,
Database Testing,
Exploratory Testing,
Mobile Application Testing.
3

Functionality Testing:
• Functional testing verifies that each function of the
software application operates in conformance with
the requirement specification.
• This testing mainly involves black box testing and it
• This testing mainly involves black box testing and it
is not concerned about the source code of the
application.
• Functions are tested by feeding them input and
examining the output, and internal program structure
is rarely considered.
4

• Each and every functionality of the system is tested
by providing appropriate input, verifying the output
and comparing the actual results with the expected
results.
• This testing involves checking of User Interface, APIs,
Database, security, client/ server applications and
functionality of the Application Under Test.
• The testing can be done either manually or using
automation tools.
5

The prime objective of Functional testing is checking the
functionalities of the software system. It mainly concentrates on
Mainline functions: Testing the main functions of an application
Basic Usability: It involves basic usability testing of the system. It
checks whether an user can freely navigate through the screens
checks whether an user can freely navigate through the screens
without any difficulties.
Accessibility: Checks the accessibility of the system for the user
Error Conditions: Usage of testing techniques to check for error
conditions. It checks whether suitable error messages are
displayed.
6

Functional Testing Process:
Functional testing process includes the following steps
1. Understand the Requirements
2. Identify test input (test data)
3. Compute the expected outcomes with the selected test
input values
4. Execute test cases
5. Comparison of actual and computed expected result
7

Functional Testing Tools
• Functional test automation tools differ from test
evaluation tools.
• They focus on “black box” tests, while test evaluation
tools are used for “white box” test.
• Functional test automation tools do not inspect the
application source code.
• Some of the functional testing tools are listed below.
• Junit, SoupUI, Watir, QTP, Win Runner, Xenu etc.
8

SQA_Unit 3.pdf it is a database education

Performance Testing
• Web application should sustain to heavy load.
• To check whether system meets performance
requirements.
• Web performance testing should include:
• Web performance testing should include:
1) Web Load Testing
2) Web Stress Testing
10

Performance Testing
• Test application performance on different internet
connection speed, Access in different browsers,
• In web performance testing web site functionality
on different operating systems,
• different hardware platforms is checked for
software,
• hardware memory leakage errors etc.
11

Performance Testing
• In web load testing test if many users are accessing
or requesting the same page.
• So, can system sustain in peak load times?
• Site should handle many simultaneous user
requests,
requests,
• large input data from users,
• Simultaneous connection to DB,
• heavy load on specific pages etc. 12

Performance Testing
• In web stress testing is performed to break the site
by giving stress
• and checked how system reacts to stress and how
system recovers from crashes.
• Stress is generally given on input fields, login and
sign up areas.
13

Performance Testing
• Example: if an app is build for 500 users,
• then for load testing we check up to 500 users
• and for stress testing we check greater than 500.
14

Security Testing
• Security is most important for all web based
application or database.
• Can system be entered by any hacking way.
• Testing how well the system protects against
unauthorized internal or external access.
unauthorized internal or external access.
• Checked if system, database is safe from external
attacks.
16

Security Testing
• Following are some test cases for web security
testing:
• Test by pasting internal URL directly into browser
address bar without login. Internal pages should
not open.
• Try some invalid inputs in input fields like login
• Try some invalid inputs in input fields like login
username, password, input text boxes.
• Check the system reaction on all invalid inputs.
• Web directories or files should not be accessible
directly unless given download option. 17

Security Testing
• The six basic security concepts that need to be
covered by security testing are
• confidentiality:
• Integrity:
• Authentication:
• Authentication:
• Availability:
• Authorization:
• non-repudiation:
18

Security Testing
• confidentiality: which protects against the
disclosure of information
• Integrity: to allow the receiver to determine
that the information which it is providing is
that the information which it is providing is
correct.
• Authentication: confirming the identity of a
person
19

Security Testing
• Availability: Assuring information and
communications services will be ready for use
when expected.
• Authorization: Access control is an example of
authorization
authorization
• non-repudiation: to ensure that a transferred
message has been sent and received by the
parties claiming to have sent and received the
message
20

Usability Testing:
Test for navigation:
• Navigation means how the user surfs the web
pages,
• different controls like buttons, boxes or
• how user using the links on the pages to surf
different pages.
22

Usability Testing:
Usability testing includes:
• Web site should be easy to use.
• Instructions should be provided clearly.
• Check if the provided instructions are correct
means whether they satisfy purpose.
• Main menu should be provided on each page.
• It should be consistent.
23

Usability Testing:
Content checking:
• Content should be meaningful.
• All the anchor text links should be working properly.
• Images should be placed properly with proper sizes.
Check that contents are relevant.
• All link are properly worked or not
25

Localization testing:
• localization testing are not strictly a part of the
development of world-ready software,
• localization becomes possible once you have
developed world-ready software.
developed world-ready software.
• Localization is the process of customizing a
software application
• that was originally designed for a domestic market.
27

Localization testing:-
• This process involves translating all native
language strings to the target language
• and customizing the GUI so that it is appropriate
for the target market.
• Localization is a process of adapting
internationalized software for a specific region or
language by adding local specific components and
translating text
28

Volume Testing:
• Volume Testing is a type of non-functional tests
• Volume testing refers to testing a software
application or the product with a certain amount of
data.
• to determine system performance with increasing
volumes of data in the database
• Volume testing is quite different from stress and
load testing.
30

Volume Testing:
• Imagine that you are testing a online shopping site,
where the volume test will be defined as:
• 1. Test the site behavior when there are more than
10,000 laptops are available under the 'laptops'
category.
category.
• 2. Testing the caller tunes-> where thousands of
songs are available for an user to download.
• Basically it deals with amount of resources.
31

Documentation testing :
• This is one of the most cost effective approaches to
testing.
• Documentation testing can start at the very
beginning of the software process
• If Documentation is right hence save large amounts
of money otherwise many problems to create after
the start or implement software process
• Because the after a defect is found it will cost to be
high to solve defect. 33

Documentation testing:
• The documentation can be tested in a number of
different ways to many different degrees of
complexity.
• These range from running the documents through a
• These range from running the documents through a
spelling and grammar checking device,
• to manually reviewing the documentation
• To documentation are tested by documentation
tool
• to remove any ambiguity or conflict.
34

Database testing:
• Database testing involves the retrieved
values from the database by the web or
desktop application.
• Data in the User Interface should be matched
• Data in the User Interface should be matched
as per the records are stored in the database.
36

Database testing:
• It performs module testing of database functions,
triggers, views, SQL queries etc.
• It validates database tables, data models,
database schema etc.
database schema etc.
• It checks rules of Referential integrity.
37

Exploratory testing:
• The main advantage of exploratory testing is that
• less preparation is needed,
• important bugs are found quickly, and
• at execution time, the approach tends to be more
• at execution time, the approach tends to be more
logically stimulating than execution of scripted
tests.
39

Exploratory testing :
• Exploratory testing has always been performed by
skilled testers because they used quality of testing
techniques and find defect easy.
• Exploratory testing seeks to find out how the
• Exploratory testing seeks to find out how the
software actually works.
40

User Acceptance testing :
• Normally this type of testing is done to verify
if system meets the customer specified
requirements.
• User or customer do this testing to determine
• User or customer do this testing to determine
whether to accept application.
42

Regression Testing:
• The purpose of regression testing is to confirm that a
recent program or code change has not adversely
affected existing features.
• Regression testing is nothing but full or partial
• Regression testing is nothing but full or partial
selection of already executed test cases
•which are re-executed to ensure existing
functionalities work fine.
44

Regression Testing:
• This testing is done to make sure that new code changes
should not have side effects on the existing functionalities.
• It ensures that old code still works once the new code
changes are done.
Regression Testing is required when there is a,
Regression Testing is required when there is a,
• Change in requirements and modifying the code according
to the requirement
• New feature is added to the software
• Defect fixing
• Performance issue fix
45

Mobile Application Testing:
• Mobile device testing is the process by which mobile
apps are tested for functionality, usability, performance
and much more.
• Testing app on mobile devices can be done manually or
with automation.
with automation.
• and helps you ensure that the application you’re
delivering to users meets all business requirements as
well as user expectations.
47

Types of Mobile Apps
• There are three general categories of mobile applications
that you may need to test today:
• Native Apps: are designed specifically for a particular
mobile platform (today this typically means either
mobile platform (today this typically means either
Android or iOS)
• and are generally downloaded and installed via an app
store like Apple’s App Store or Google’s Play Store.
• This includes both pure native apps built on Java/Kotlin
for Android or Objective-C/Swift for iOS
48

• Responsive Web Apps are designed to be accessed on a
mobile browser.
• Web apps can be either a responsive version of a website
• Web apps can be either a responsive version of a website
or a progressive web app (PWA),
•which adds additional mobile-friendly features.
49

• Hybrid Apps are designed as a compromise between
native and web apps.
•Hybrid apps can be installed via app stores just like
•Hybrid apps can be installed via app stores just like
native apps and may have some native functionality,
•but at least partially rely on operating essentially as web
apps wrapped in a native shell.
50

Black box testing – Internal system design is not considered in this type of
testing. Tests are based on requirements and functionality.
White box testing – This testing is based on knowledge of the internal logic
of an application’s code. Also known as Glass box Testing. Internal software
and code working should be known for this type of testing. Tests are based
on coverage of code statements, branches, paths, conditions.
Unit testing – Testing of individual software components or modules.
Typically done by the programmer and not by testers, as it requires
Typically done by the programmer and not by testers, as it requires
detailed knowledge of the internal program design and code. may require
developing test driver modules or test harnesses.
Integration testing – Testing of integrated modules to verify combined
functionality after integration. Modules are typically code modules,
individual applications, client and server applications on a network, etc.
This type of testing is especially relevant to client/server and distributed
systems.
53

System testing – Entire system is tested as per the requirements. Black-
box type testing that is based on overall requirements specifications,
covers all combined parts of a system.
End-to-end testing – Similar to system testing, involves testing of a
complete application environment in a situation that mimics real-world
use, such as interacting with a database, using network
communications, or interacting with other hardware, applications, or
systems if appropriate.
Acceptance testing -Normally this type of testing is done to verify if
system meets the customer specified requirements. User or customer
do this testing to determine whether to accept application.
Install/uninstall testing – Tested for full, partial, or upgrade
install/uninstall processes on different operating systems under
different hardware, software environment.
54

Performance testing – Term often used interchangeably with ‘stress’
and ‘load’ testing. To check whether system meets performance
requirements. Used different performance and load tools to do this.
Load testing – Its a performance testing to check system behavior under
load. Testing an application under heavy loads, such as testing of a web
site under a range of loads to determine at what point the system’s
response time degrades or fails.
Stress testing – System is stressed beyond its specifications to check
Stress testing – System is stressed beyond its specifications to check
how and when it fails. Performed under heavy load like putting large
number beyond storage capacity, complex database queries, continuous
input to system or database load.
Security testing – Can system be penetrated by any hacking way. Testing
how well the system protects against unauthorized internal or external
access. Checked if system, database is safe from external attacks.
55

Compatibility testing – Testing how well software performs in a
particular hardware/software/operating system/network environment
and different combination s of above.
Comparison testing – Comparison of product strengths and weaknesses
with previous versions or other similar products.
Alpha testing – In house virtual user environment can be created for
this type of testing. Testing is done at the end of development. Still
minor design changes may be made as a result of such testing.
minor design changes may be made as a result of such testing.
Beta testing – Testing typically done by end-users or others. Final testing
before releasing application for commercial purpose.
Happy Testing!!!
56

Usability testing – User-friendliness check. Application flow is tested,
Can new user understand the application easily, Proper help
documented whenever user stuck at any point. Basically system
navigation is checked in this testing.
Recovery testing – Testing how well a system recovers from crashes,
hardware failures, or other catastrophic problems.
Incremental integration testing – Bottom up approach for testing
Incremental integration testing – Bottom up approach for testing
i.e. continuous testing of an application as new functionality is added;
Application functionality and modules should be independent enough
to test separately.
done by programmers or by testers.
57

Functional testing – This type of testing ignores the internal parts and
focus on the output is as per requirement or not. Black-box type
testing geared to functional requirements of an application.
Sanity testing – Testing to determine if a new software version is
performing well enough to accept it for a major testing effort. If
application is crashing for initial use then system is not stable enough
for further testing and build or application is assigned to fix.
Regression testing – Testing the application as a whole for the
modification in any module or functionality. Difficult to cover all the
system in regression testing so typically automation tools are used for
these testing types.
58

SQA_Unit 3.pdf it is a database education

More Related Content

Similar to SQA_Unit 3.pdf it is a database education (20)

More from RAVALCHIRAG1 (13)

Recently uploaded (20)

SQA_Unit 3.pdf it is a database education