Scribd
Upload
134 views2 pages

Levels and Types of Software Testing

The document outlines six levels of testing that will be executed for Release 8.0: unit testing, functional system testing, integrated system testing, browser testing, performance testing, regression testing, user acceptance testing, and post-deployment check-out. It also describes the objectives and purpose of functional system testing, integrated system testing, user acceptance testing, and regression testing. These types of testing aim to verify requirements, ensure the system functions as intended, validate user needs are met, and check that new releases do not impact previous functionality.

Uploaded by

Rajesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
134 views2 pages

Levels and Types of Software Testing

The document outlines six levels of testing that will be executed for Release 8.0: unit testing, functional system testing, integrated system testing, browser testing, performance testing, regression testing, user acceptance testing, and post-deployment check-out. It also describes the objectives and purpose of functional system testing, integrated system testing, user acceptance testing, and regression testing. These types of testing aim to verify requirements, ensure the system functions as intended, validate user needs are met, and check that new releases do not impact previous functionality.

Uploaded by

Rajesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

2.21.

1 Levels of Testing Formatted: Bullets and Numbering

The following six levels of testing will be executed in Release 8.0:


 Unit test (Development)
 Functional System Test (QA)
 Integrated System Test (QA)
 Browser Testing (QA)
 Performance Testing (QA)
 Regression Test (QA)
 User Acceptance Test (Business)
 Post-Deployment Check-out (QA)

2.31.2 Types of Testing Formatted: Bullets and Numbering

2.3.11.2.1 Functional System Test


The purpose of a System Test is to verify that technical and functional system
components can process as one system. System Test begins when an Infrastructure
Test has been conducted to ensure all technical system components of the
customized solution have been completely implemented. Once integrated, the
system is tested to ensure the system functions as designed. Completion of a
System Test occurs when all functional system components have been integrated
into the system and have successfully passed all integrated verification.
Objectives of a System Test:
 Verify the requirements defined in the Business Requirements have been
met
 Ensure the integrated system can process as one system
 Ensure the application is of high quality
 Ensure the software will support the intended business functions and
achieves the standards required by the company for the development of
new systems
 Ensure the application delivered interfaces correctly with existing
systems

1.2.2 Integrated System Test (IST)


The purpose of an Integrated System Test is to verify the functional and technical
system components between two interfaces. It is conducted to verify that
interfaces can process as one system.
Objectives of an Integrated System Test:
 Analyze exception reports to ensure errors are identified
 Validate file formats and file content
 Verify audit stamps, error messages, and files sent to/from the interface
 Verify data can be received and transmitted to/from the interface
 Verify hardware is set up and configured properly
 Verify software is installed and connectivity is established to the
interface
1.2.3 User Acceptance Test (UAT)
The purpose of UAT is to provide user representatives an opportunity to perform
various tests to ensure the system meets the needs of the company. After all the
tests have been successfully performed, the system is ready for general availability.
Objectives of a User Acceptance Test (UAT):
 Validate that the system functions as specified by the business
 Validate that the customer’s business requirements for the system have
been met as defined in the Business Requirements Document (BRD)
 Ensure the application meets the client’s needs and specifications

1.2.4 Regression Test


The purpose of regression testing is to ensure that there is an increase in the
functionality and stability of the software. It allows a consistent, repeatable
validation of each new release of a product.
Objectives of a Regression Test:
 Validate that the release of the software has no impact on previously
released software or systems
 Ensure reported product defects have been corrected for each new
release and that no new quality problems were introduced in the
maintenance process

You might also like