Scribd
Upload
34 views

Testing Methods: Group Members: Amol Chavan (6) Latika Sruthi Panicker

The document discusses various software testing methods including system testing, usability testing, performance testing, load testing, security testing, and configuration testing. System testing verifies that a complete integrated system meets requirements from the end user's perspective. It involves testing various usage scenarios and configurations. Usability testing evaluates how easily users can use the interface. Performance, load, and stress testing check how the system performs under heavy usage loads and determine breaking points. Security testing verifies that only authorized users can access permitted features. Configuration testing ensures the software works as intended across different hardware configurations.

Uploaded by

swamipanjala
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
34 views

Testing Methods: Group Members: Amol Chavan (6) Latika Sruthi Panicker

The document discusses various software testing methods including system testing, usability testing, performance testing, load testing, security testing, and configuration testing. System testing verifies that a complete integrated system meets requirements from the end user's perspective. It involves testing various usage scenarios and configurations. Usability testing evaluates how easily users can use the interface. Performance, load, and stress testing check how the system performs under heavy usage loads and determine breaking points. Security testing verifies that only authorized users can access permitted features. Configuration testing ensures the software works as intended across different hardware configurations.

Uploaded by

swamipanjala
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Testing Methods

Group members: Amol Chavan(6)


Latika

Sruthi Panicker
The testing methods can be broadly divided into two
categories the Verification and Validation methods.

 Validation methods
1. Unit Testing
2. Integration Tesing
3. Functional Testing
4. System Testing
5. Acceptance Testing
System Testing
System testing is one of the most difficult activities.
System testing is conducted on a complete, integrated
system to evaluate the system’s compliance with its
specified requirements.
It verifies from the perspective of the end user, with
different configuration.
It falls within the scope of Black Box testing.
It begins with software components that have cleared
Unit and Integration testing.
The steps of system testing are:

Decompose and analyze the SRS.


Partition the requirements.
Determine inputs and outputs for requirements.
Develop the requirement test cases.
Develop a requirement coverage matrix which is simply
a table that maps the requirements with the test cases.
Execute the test cases and measure the logic coverage.
Develop additional tests, as indicated by the combined
coverage information.
 The various System Testing types are:

1. Usability testing
2. Performance testing
3. Load testing
4. Security testing
5. Configuration testing
Usability Testing
It is the process of attempting to identify
discrepancies between the user interface of a product
and the human engineering requirements of its
potential users.
It involves, having users work with the product and
observing their responses to it.
The goal of usability testing is to adapt software to
meet user’s actual work styles, rather than forcing
users to adapt new work style.
Usability testing can be done numerous times during
the life cycle.
Performance Testing
It is a testing to ensure that the application responds in the
time limit set by the user.
It is to determine whether the program meets its
performance requirements.
The purpose of performance testing is to partially validate
the system, to cause failures relating to performance
requirements, capacity, response time.
Report these failures to the development teams so that
defect can be fixed.
Help determine the extent to which the system is ready foe
launch.
Load Testing
Testing an application under heavy loads, in order to
determine at what point the system’s response time
degrades or fails.
 Load testing is important so as to measure and
monitor performance of the system, avoid project
failures.
Load Runner and Rational Robot are the front runners
for this type of testing.
Security Testing
Security testing is performed to guarantee that only
users with the appropriate authority are able to use the
applicable features of the system.
The purpose is to determine how well a system
protects against unauthorized internal or external
access or willful damage.
It is to test whether the system meets its specified
security objectives.
Tester’s aim is to demonstrate the system’s failure to
fulfill the, stated security requirements.
Configuration Testing
Configuration testing is the process of checking the
operation of the software you are testing with all these
various types of hardware.

The purpose is that whether the program operates


properly when the hardware or software is configured
in a required manner.
Acceptance Testing
Acceptance testing is the process of evaluating the product with
the current needs of its end users. It is usually done by end users
or customers after the testing group has successfully completed
the testing.

The objective of acceptance testing is to:


Determine whether the application satisfies its acceptance
criteria.
Enable the customer organization to determine whether to accept
the application.
Report any failures to the development teams so that defects can
be fixed.
Acceptance testing can be done in two ways:
ALPHA testing
BETA testing

ALPHA testing
It is usually performed by the end users inside the
development organization.
It is done in a controlled environment.
Developers are present.
The defects are noted by the development team and
then it is fixed before release.
BETA testing
It is usually performed by end users outside the
development organization and inside the end users
organization.
Environment is not under control.
Developers are not present.
The defects found by the end user are reported to the
development organization.
Once the acceptance testing is done the user gives
clearance to release the software.
Independent Testing

You might also like