this presentation is about testing of software.

1. SOFTWARE QUALITY ASSURANCE
Submitted by :
 Farah Gulzar,
 Usama Riaz &
 Gohar Ali Shah
Submitted To :
 Sir Hafiz
Zeeshan

2. SOFTWARE QUALITY ASSURANCE
Submitted by :
 Farah Gulzar,
 Usama Riaz &
 Gohar Ali Shah
Submitted To :
 Sir Hafiz
Zeeshan

3. Introduction to testing:
.
Software QA (quality assurance) testing is the process of
evaluating the functionality of a software application to find
any bugs or issues. It analyses whether the developed
software has met requirements and identifies any defects in
the software, so that a high-quality product can be made.

4. Verification :
Verification evaluates software artifacts (such as
requirements, design, code, etc.) to ensure they
meet the specified requirements and standards.
Verification:Are we building the product Right?

5. Validation:
Validation testing is the process of assessing a new
software product to ensure that its performance
matches consumer needs. Product development team
might perform validation Testing.
validation:Are we building the right product?

6. What is right?
• Standard or specifications to measure or identify Correct
results from incorrect results or must define must terms:
1. Mistake
2. Fault
3. Error
4. Failure
5. Specification

7. The economics of software testing
• In software development there are costs associated
with Testing our programs
Cost of Quality: Cost of quality is a term that is
used to quantify the total cost of failure, appraisal,
and prevention costs associated with the
production of software.
goal of testing Covering many defects As possible
with a little testing

8. The basics of Software testing
• Software testing is the process of evaluating
and verifying that a software product or
application does what it is supposed to do. The
benefits of testing include preventing bugs,
reducing development costs and improving
performance.

9. Types of testing
• There are two types of testing
• Unit testing
• Integration testing
Unit testing:
Unit testing is a type of software testing which is done on an
individual unit or component to test its corrections. Typically,
Unit testing is done by the developer at the application
development phase.

10. Integration testing
• Integration testing is a type of software testing where
two or more modules of an application are logically
grouped together and tested as a whole. The focus of this
type of testing is to find the defect on interface,
communication, and data flow among modules. Top-down
or Bottom-up approach is used while integrating modules
into the whole system.

11. Acceptance testing
• Acceptance testing is done by the
customers to check whether the
delivered products perform the desired
tasks or not, as stated in requirements.

12. System testing
• System Testing is carried out on the
whole system in the context of either
system requirement specifications or
functional requirement specifications or in
the context of both.

13. Functional testing
• Equivalence Tests. Test data is segregated into
partitions called equivalence data Case
•

14. Regression testing
• Regression testing is a type of testing where you
can verify that the changes made in the codebase
do not impact the existing software functionality.

15. Beta testing
• Beta testing is a type of User Acceptance Testing
among the most crucial testing, which performed
before the release of the software. Beta Testing is
a type of Field Test. This testing performs at the
end of the software testing life cycle

16. Advantages
• Saves Your Money.
• Inspires Client Confidence.
• Maintains Great User Experience.
• Brings In More Profit.
• Boosts Customer Satisfaction.
• Promotes Organization, Productivity, and Efficiency.

17. Disadvantages
• Most testing types are time-consuming due to executing
tests continuously.
• Lack of experienced software and QA testers who are
aware of testing techniques.
• The software testing team requires many members.
• Increases the cost of the software and the budget.