The document discusses various types of software testing that take place during the software development life cycle (SDLC). It defines key terms like bugs, faults, and failures. It then explains different types of testing like unit testing, system testing, usability testing, functional testing, security testing, alpha testing, acceptance testing, beta testing, regression testing, and monkey testing. The overall purpose of software testing is to identify issues, ensure quality, and validate that requirements are met before releasing the software to end users.

1. Farhanullah khan
(0895) BSSE

2. Agenda:-
 Introduction
 Importance of testing in SDLC
 Testing life cycle
 Types of testing
 Verification & Validation

4. Software testing is a process used to identify the
correctness, completeness and quality of developed
computer software.
It is the process of executing a program /
application under positive and negative conditions
by manual or automated means. It checks for the :-
 Specification
 Functionality
 Performance
Software Testing

5.  Software Testing is important as it may
cause mission failure, impact on
operational performance and reliability if
not done properly.
Why Software is Testing ?

6. Bug, Fault & Failure
• Error : An error is a human action that produces the incorrect result that
results in a fault.
• Bug : The presence of error at the time of execution of the software.
• Fault : State of software caused by an error.
• Failure : Deviation of the software from its expected result. It is an event.
A person makes an Error
That creates a fault in software
That can cause a failure in operation

7. Who is a Software
Tester??..
 Software Tester is the one who performs testing
and find bugs, if they exist in the tested
application.

9. When to Start Testing in
SDLC
 Requirement
 Analysis
 Design
 Coding
 Testing
 Implementation
 Maintenance

11. Unit Testing
 Test each module individually.
 Follows a white box testing.
 Done by Developers.

12. System Testing
 After completing Unit and Integration testing
through white box testing techniques development
team release an .exe build (all integrated module) to
perform black box testing.
 Usability Testing
 Functional Testing
 Performance Testing
 Security Testing

13. Usability Testing
 During this test, testing team concentrates
on the user friendliness of build interface.

14. Functional Testing
 The process of checking the
behavior of the application.
 To check the correctness of
outputs.
 Data validation and Integration
i.e. inputs are correct or not.

15. Security Testing
 Testing how well the system
protects against unauthorized
internal or external access, willful
damage etc .

16. Alpha Testing
 The application is tested by the users who doesn’t know about
the application.
 Done at developer’s site under controlled conditions
 Under the supervision of the developers.

17. Acceptance Testing
 A formal test conducted to determine whether or not a
system satisfies its acceptance criteria and to enable the
customer to determine whether or not to accept the system.

18. Beta Testing
 This Testing is done before the final
release of the software to end-users.

19. Regression Testing
 Testing with the intent of
determining if bug fixes have been
successful and have not created any
new problems.
 Also this type of testing is done to
ensure that no degradation of
baseline functionality has occurred.

20. Monkey Testing
 Testing the application randomly like
hitting keys irregularly and try to
breakdown the system.
 There is no specific test cases and scenarios
for monkey testing.