Software testing fundamentals for the

1. Software
Testing

3. Definition of
testing?

5. Who does testing?

6. Why testing is
important?

7. Software
development
life cycle (SDLC)

8. SDLC Models
• Waterfall model
• V-model
• Spiral Model
• Prototype Model
• Hybrid Model

11. Spiral Model

12. The rest of the SDLC models we’ve chosen fall under the
umbrella of Agile. Nowadays, more than 70% of organizations
employ this or that Agile approach in their IT projects. In
general, at the heart of Agile are iterative
development(Incremental and Iterative model), intensive
communication, and early customer feedback.

13. Software
Testing
Principles

14. Software
Testing Life
Cycle (STLC)

15. Types of testing

19. White-box testing
techniques:
• Data Flow Testing
• Control Flow Testing
• Branch Coverage Testing
• Statement Coverage Testing
• Decision Coverage Testing

20. Black-box test design
techniques:
• Decision table testing.
• All-pairs testing.
• Equivalence partitioning.
• Boundary value analysis.
• Cause–effect graph.
• Error guessing.
• State transition testing.
• Use case testing.
Exhaustive testing is not possible every time so below
techniques are useful to do testing.

22. Verification & Validation
• Verification is termed as static technique and it does not involve in any execution of
code , program or product. It is a manual process and normally occurs during the
requirements, design, and program
• Validation testing is testing where tester performed functional and non-functional
testing. Here functional testing includes Unit Testing (UT), Integration Testing (IT) and
System Testing (ST), and User acceptance testing (UAT).

23. Methods of Verification
• Self Review
• Peer Review
• Superior Review
• Walkthrough
• Inspection (Formal Review)
• Audits

24. Levels of
testing

26. How to find
bugs ?

28. Test Data Management &
Defect tracking Tools
• TFS (Team Foundation Server)
• ALM (Application Lifecycle Management)
• ADO (Azure Devops)
• JIRA

29. Bug Reporting

30. Bug Title: Forgot password option is missing.
Bug ID: (It will be automatically created by the BUG
Tracking tool once you save this bug)
Area Path: username->password->forgot
password.(or) a specific scrum team
Iteration Path: current sprint number
Build Number: (Generates automatically when dev
deploys the bug)
Severity: (Critical/ High/Medium/Low)
Priority: (Critical/ High/Medium/Low) or (1 to 4)
Assigned to: Developer-X
Reported(created) By: Your Name
Reported (created) On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you
are using)
Environment:
Description:. Missing “Forgot password” option
Screenshot/video: For better understanding of bug
Recreation steps: steps to recreate the bug
Removal/closer Reason: Given by SM or dev while
removing or closing the bugs
Root cause: provided by DEV
Tags: different tag to classify bugs

32. Software
Testing
Documentation

33. What is an Exit Criteria?
Exit criteria is used to determine whether a given test activity has been completed or
NOT. Exit criteria can be defined for all of the test activities right from planning,
specification and execution.
Exit criterion should be part of test plan and decided in the planning stage.
Examples of Exit Criteria:
 Verify if all tests planned have been run.
 Verify if the level of requirement coverage has been met.
 Verify if there are NO Critical or high severity defects that are left outstanding.
 Verify if all high-risk areas are completely tested.
 Verify if software development activities are completed within the projected cost.
 Verify if software development activities are completed within the projected
timelines.

35. Automation
Testing!!

37. Different
automation
testing tools