The document discusses software testing fundamentals including why testing is needed, different types of documentation for testing, benefits of writing test cases, common software development models like waterfall, spiral and V-model, levels of testing from unit to acceptance, and strategic approaches to testing involving verification and validation. It emphasizes that testing ensures quality, reduces costs and time, and helps find defects to meet business and user requirements.

1. SOFTWARE TESTING FUNDAMENTALS

2. Agenda
Documentation in Testing
What is Testing?
2
Why do we need Testing?
3
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
4
Strategic Approach
6
Levels of Testing
7
Models
5
SDLC - Process
1

3. Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
SDLC - Process

4. SDLC
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
Planning
Designing
Construction
Testing
Maintenance
Raw materials requirement

5. What is Testing?
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

6. What is Testing?
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
● Testing can be defined as “Performing Verification and Validation of the Software Product” for its correctness
and accuracy of working.
● Software Testing is to identify errors in order to reveal and spot it.

7. Why do we need
Testing?
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

8. Why do we need Testing?
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
● To save time as well as cost.
● To provide best quality product without taking so much time and money.
● To find defects which may get created by the programmer while developing the software.
● To gain confidence in and providing information about the level of quality.
● To prevent defects.
● To make sure that the end result meets the business and user requirements.

9. Documentation in
Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

10. Documentation in Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
• Found the issue
• Created a bad situation for the company
• Issue – Compatibility of one website
• Issue was presented to higher authorities
• They showed the client a written proof
• Issue was resolved peacefully

11. Documentation in Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
The prime objective of any software project is to get a high-quality output while reducing the cost and the time
required for completing the project. To achieve that, companies test their software before they release it to the
market. Documentation plays a critical role in achieving effective software testing
There are different levels of documentation, like:
Test Script: A line-by-line description of all the actions and data needed to perform a test.
Test Case: Describes a specific idea that is to be tested, without detailing the exact steps to be taken or data to be
used.
Test Scenario: It is a simple description of an objective a user might face when testing.
A test case is a document which has a set of conditions or actions that
are performed on the software application in order to verify the
expected functionality of the feature.

12. Benefits of Writing Test Cases
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
The key purpose of a test case is to ensure if different features within an application are working as expected. It
helps tester, validate if the software is free of defects and if it is working as per the expectations of the end users.
Other benefits of test cases include:
• Test cases ensure good test coverage
• Help improve the quality of software,
• Decreases the maintenance and software support costs
• Help verify that the software meets the end user requirements
• Allows the tester to think thoroughly and approach the tests from as many angles as possible
• Test cases are reusable for the future – anyone can reference them and execute the test.

13. Models
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

14. Waterfall Model
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

15. Spiral Model
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
Concept Development
System Development
System Enhancement
System Maintenance

16. V Model
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

17. Strategic Approach
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

18. Strategic Approach to Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
General Characteristics of Strategic Testing :-
• To perform effective testing, a software team should conduct technical reviews.
• Testing begins at the component level and work toward the integration of entire computer based system.
• Different testing techniques are appropriate at different points in time.
• Testing is done by developer of Software and for large projects by an independent test group.
• Testing and Debugging are different activities, but debugging must be accommodated in any test strategy.

19. Strategic Approach to Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
In other words, software testing is a verification and validation process :-
Verification – Does the product meet its specifications?
The set of activities that ensure that software correctly implements a specific function or algorithm.
Validation – Does the product perform as desired?
The set of activities that ensure that the software which has been built is traceable to customer requirements.

20. Strategic Approach to Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
System
Project
Sub Modules
Modules
Unit Testing
Integration Testing
Validation Testing
System Testing

21. Levels of Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited

22. Levels of Testing
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited
UNIT TESTING
INTEGRATION
TESTING
SYSTEM
TESTING
REGRESSION
TESTING
ACCEPTANCE
TESTING
DEVELOPER
DEVELOPER / TESTER
TESTER

23. Thank You
Proprietary content. ©Great Learning. All Rights Reserved. Unauthorized use or distribution prohibited