Scribd
Upload
33 views

Software Testing - Validation Testing

Validation testing ensures that a software product meets the needs of the client. It evaluates the product during or after development to determine if it satisfies business requirements. Validation testing can be demonstrated using the V-Model and evaluates the software or product under test. It answers whether the right product is being built.

Uploaded by

Sumit Negi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
33 views

Software Testing - Validation Testing

Validation testing ensures that a software product meets the needs of the client. It evaluates the product during or after development to determine if it satisfies business requirements. Validation testing can be demonstrated using the V-Model and evaluates the software or product under test. It answers whether the right product is being built.

Uploaded by

Sumit Negi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

 Software Testing - Validation Testing

The process of evaluating software during the development process or at the end of
the development process to determine whether it satisfies specified business
requirements.
Validation Testing ensures that the product actually meets the client's needs. It can
also be defined as to demonstrate that the product fulfills its intended use when
deployed on appropriate environment.
It answers to the question, Are we building the right product?

Validation Testing - Workflow:


Validation testing can be best demonstrated using V-Model. The Software/product
under test is evaluated during this type of testing.
What is Unit Testing?
Unit testing, a testing technique using which individual modules are tested to determine
if there are any issues by the developer himself. It is concerned with functional
correctness of the standalone modules.
The main aim is to isolate each unit of the system to identify, analyze and fix the
defects.

Unit Testing - Advantages:


 Reduces Defects in the Newly developed features or reduces bugs when changing the
existing functionality.
 Reduces Cost of Testing as defects are captured in very early phase.
 Improves design and allows better refactoring of code.
 Unit Tests, when integrated with build gives the quality of the build as well.

Unit Testing Techniques:


 Black Box Testing - Using which the
user interface, input and output are
tested.
 White Box Testing - used to test
each one of those functions
behaviour is tested.
 Gray Box Testing - Used to execute
tests, risks and assessment methods.
 Previous 

Unit Testing LifeCyle:


What is Integration Testing?
Upon completion of unit testing, the units or modules are to be integrated which gives
raise to integration testing. The purpose of integration testing is to verify the functional,
performance, and reliability between the modules that are integrated.

Integration Strategies:
 Big-Bang Integration
 Top Down Integration
 Bottom Up Integration
 Hybrid Integration

What is System Testing?


System Testing (ST) is a black box testing technique performed to evaluate the
complete system the system's compliance against specified requirements. In System
testing, the functionalities of the system are tested from an end-to-end perspective.
System Testing is usually carried out by a team that is independent of the development
team in order to measure the quality of the system unbiased. It includes both functional
and Non-Functional testing.

Types of System Tests:


What is User Acceptance Testing?
User acceptance testing, a testing methodology where the clients/end users involved in
testing the product to validate the product against their requirements. It is performed at
client location at developer's site.
For industry such as medicine or aviation industry, contract and regulatory compliance
testing and operational acceptance testing is also carried out as part of user
acceptance testing.
UAT is context dependent and the UAT plans are prepared based on the requirements
and NOT mandatory to execute all kinds of user acceptance tests and even
coordinated and contributed by testing team.

User Acceptance Testing - In SDLC


The following diagram explains the fitment of user acceptance testing in the software
development life cycle:

The acceptance test cases are executed against the test data or using an acceptance
test script and then the results are compared with the expected ones.
Acceptance Criteria
Acceptance criteria are defined on the basis of the following attributes:
 Functional Correctness and Completeness

 Data Integrity

 Data Conversion

 Usability

 Performance

 Timeliness

 Confidentiality and Availability

 Installability and Upgradability

 Scalability

 Documentation

Acceptance Test Plan - Attributes


The acceptance test activities are carried out in phases. Firstly the basic tests are
executed and if the test results are satisfactory then the execution of more complex
scenarios are carried out.
The Acceptance test plan has the following attributes
 Introduction

 Acceptance Test Category

 operation Environment

 Test case ID

 Test Title

 Test Objective

 Test Procedure

 Test Schedule

 Resources

The acceptance test activities are designed to reach at one of the conclusions :
1. Accept the system as delivered
2. Accept the system after the requested modifications have been made
3. Do not accept the system
Acceptance Test Report - Attributes
The Acceptance test Report has the following attributes:
 Report Identifier

 Summary of Results

 Variations

 Recommendations

 Summary of To-DO List

 Approval Decision

You might also like