Scribd
Upload
64 views

Netsol Technology Institute - Nti: Sessions 4 Testing Types

The document discusses different types of software testing including functional testing, non-functional testing, sanity testing, performance testing, stress testing, usability testing, security testing, recovery testing, installation testing, and end-to-end testing. Each testing type has specific goals such as evaluating how the software handles different loads, recovers from failures, or interacts with other systems. The overall purpose is to ensure software meets requirements and performs as expected under various conditions.

Uploaded by

magillani
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
64 views

Netsol Technology Institute - Nti: Sessions 4 Testing Types

The document discusses different types of software testing including functional testing, non-functional testing, sanity testing, performance testing, stress testing, usability testing, security testing, recovery testing, installation testing, and end-to-end testing. Each testing type has specific goals such as evaluating how the software handles different loads, recovers from failures, or interacts with other systems. The overall purpose is to ensure software meets requirements and performs as expected under various conditions.

Uploaded by

magillani
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 17

NETSOL TECHNOLOGY INSTITUTE - NTI

Sessions 4
Testing Types

www.netsoltek.com
www.netsoltekinstitute.com
Functional Testing

• Equivalence Partitioning
• Boundary Value Analysis
• Intrusive Testing
• Random Testing
• State Transition Analysis
• Static Testing
• Thread Testing

www.netsoltek.com
www.netsoltekinstitute.com
Non-Functional Testing

• Configuration/Installation Testing
• Compatibility & Interoperability Testing
• Documentation & Help Testing
• Graphical User Interface (GUI) Testing
• Fault Recovery Testing
• Performance Testing
• Security Testing
• Stress Testing
• Usability Testing
www.netsoltek.com
www.netsoltekinstitute.com
Sanity Testing

• Sanity testing will be performed whenever


cursory testing is sufficient to prove the
application is functioning according to
specifications.
• This level of testing is a subset of regression
testing.
• It will normally include a set of core tests of basic
GUI functionality to demonstrate connectivity to
the database, application servers, printers, etc.

www.netsoltek.com
www.netsoltekinstitute.com
Performance testing

. Performance testing - term often used interchangeably with 'stress' and 'load' testing.
Ideally 'performance' testing (and any other 'type' of testing) is defined in
requirements documentation or QA or Test Plans.

         Load testing - 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 - term often used interchangeably with 'load' and 'performance'
testing. Also used to describe such tests as system functional testing while under
unusually heavy loads, heavy repetition of certain actions or inputs, input of large
numerical values, large complex queries to a database system, etc.

www.netsoltek.com
www.netsoltekinstitute.com
Contd.

         Ad-hoc testing - similar to exploratory


testing, but often taken to mean that the testers
have significant understanding of the software
before testing it.
       
         Comparison testing - comparing software
weaknesses and strengths to competing
products.
  

www.netsoltek.com
www.netsoltekinstitute.com
Stress Testing
• Stress Testing
• Stress testing executes a system in a manner that demands resources in
abnormal quantity, frequency, or volume. The following types of tests may
be conducted during stress testing:
• Special tests may be designed that generate ten interrupts per second,
when one or two is the average rate.
• Input data rates may be increases by an order of magnitude to determine
how input functions will respond.
• Test Cases that require maximum memory or other resources.
• Test Cases that may cause excessive hunting for disk-resident data.
• Test Cases that my cause thrashing in a virtual operating system.

• Volume Testing
– Tests subject the program to a high volume of data
– Volume tests study the largest tasks the program can deal

www.netsoltek.com
www.netsoltekinstitute.com
Usability Testing

– Usability tests evaluate the ease with which a


user can learn to use a system.
– Usability can be measured in following terms:
• Skills require to learn the system
• Time required to become efficient in the use of the
system
• Net increase in the productivity

www.netsoltek.com
www.netsoltekinstitute.com
Usability Testing

• Testing for 'user-friendliness'. Clearly this is


subjective and will depend on the targeted
enduser
• or customer. User interviews, surveys, video
recording of user sessions, and other
• techniques can be used. Programmers and
testers are usually not appropriate as usability
• testers.

www.netsoltek.com
www.netsoltekinstitute.com
Exploratory Testing

– Test Design and Test Execution at the same


time
– Useful in complex situations when little is
known about the product

www.netsoltek.com
www.netsoltekinstitute.com
Security Testing

• Security testing attempts to verify that protection


mechanisms built into a system will, in fact, protect it
from improper penetration. During Security testing,
password cracking, unauthorized entry into the software,
network security are all taken into consideration.

• Security/Penetration Testing
• Testing how well the system protects against
unauthorized internal or external access, willful
• damage, etc. This type of testing may require
sophisticated testing techniques.

www.netsoltek.com
www.netsoltekinstitute.com
Recovery Testing

• Recovery testing is a system test that focuses the software to fall in


a variety of ways and verifies that recovery is properly performed. If
recovery is automatic, reinitialization, checkpointing mechanisms,
data recovery and restart are evaluated for correctness. If recovery
requires human intervention, the mean-time-to-repair (MTTR) is
evaluated to determine whether it is within acceptable limits.

• Recovery/Error Testing
• Testing how well a system recovers from crashes, hardware
failures, or other catastrophic
• problems.

www.netsoltek.com
www.netsoltekinstitute.com
Installation Testing

• Testing full, partial, or upgrade install/uninstall


processes. The installation test for a release
• will be conducted with the objective of demonstrating
production readiness. This test is
• conducted after the application has been migrated to the
client’s site. It will encompass the
• inventory of configuration items (performed by the
application’s System Administration) and
• evaluation of data readiness, as well as dynamic tests
focused on basic system functionality.
• When necessary, a sanity test will be performed
following the installation testing. `
www.netsoltek.com
www.netsoltekinstitute.com
Testing the installer

• Does the installer launch, install to the correct


location/path
• Are all the features included within the installer
• Are the correct settings enabled
• Can you utilize the uninstall feature
• If upgrading, does the installer remove old files
or create an additional folder
• Can the software launch

www.netsoltek.com
www.netsoltekinstitute.com
Parallel/Audit Testing

• Testing where the user reconciles the


output of the new system to the output of
the current
• system to verify the new system performs
the operations correctly.

www.netsoltek.com
www.netsoltekinstitute.com
End-to-End Testing

• Similar to system testing, the 'macro' end of the


test scale 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.

www.netsoltek.com
www.netsoltekinstitute.com
Compatibility Testing

• Testing how well software performs in a


particular hardware/software/operating
• system/network/etc. environment.

www.netsoltek.com
www.netsoltekinstitute.com

You might also like