Software Testing Concepts

•Verification vs. Validation

•Verification: Are we building the product right?
•Validation: Are we building the right product?
•Key Terms
•Defects: Flaws in the software.
•Test Cases: Steps for evaluating functionality
 Importance of Testing Concepts
• Improves software reliability and performance.
• Reduces cost of fixing defects later.
• Ensures user satisfaction and compliance.
 Common Testing Issues
• Ambiguous or incomplete requirements.
• Limited testing time and resources.
• Ineffective defect tracking systems.
 Addressing Testing Issues
• Define clear and complete requirements.
• Allocate time and resources efficiently.
• Use reliable tools for defect tracking
 software testing techniques
• Overview of Software Testing Techniques
• Definition:
• Methods used to evaluate software functionality and
detect defects.
 Purpose:
• Verify functionality.
• Ensure software quality.
• Identify bugs early.
 Categories:
• Static Testing:
• Reviews and inspections without execution.
• Dynamic Testing:
• Testing with code execution.
 Static Testing Techniques
• Testing without running the application
• .Focus: Finding defects in documents or code.
• Examples:
• Reviews: Evaluating documents and code.
• Walkthroughs: Step-by-step discussion with team members.
• Inspections: Formal analysis of artifacts to find defects.
• Advantages:
• Early defect detection.
• Saves development costs.
 Dynamic Testing Techniques
• Testing performed by executing the application.
• Focus: Verifying outputs against expected behavior.
• Examples:
• Functional Testing:
• Testing specific features based on requirements.
• Non-functional Testing:
• Testing quality attributes like performance, security, and
usability.
 Functional Testing Techniques
• Types:
• Black-box Testing:
• Focus: Inputs and outputs, ignoring internal logic.
• Example: Testing login functionality.
• 2. White-box Testing:
• Focus: Internal code and logic.
• Example: Path testing, loop testing.
• 3. Grey-box Testing:
• Combination of black-box and white-box testing.
• Example: Testing with partial knowledge of the code.
 Non-functional Testing
Techniques
• Performance Testing: Speed and responsiveness under
varying loads.
• Load Testing: Evaluating behavior under expected and
peak usage.
• Stress Testing: Testing under extreme conditions.
• Usability Testing: Ensuring user-friendliness and
accessibility.
• Security Testing: Identifying and fixing vulnerabilities.
 Automation vs Manual Testing
Techniques
Automation Testing: Manual Testing:
• Uses tools/scripts to • Conducted by humans for
exploratory and ad hoc testing.
execute tests (e.g.,
• Example: UI/UX testing.
Selenium, TestNG).
• Comparison:
• Example: Regression • Automation: Efficient for repetitive
testing. tasks.
• Manual: Better for complex
scenarios.
 software testing life cycle
• Introduction to Software Testing Lifecycle
• Definition:
• The sequence of phases involved in the testing process to
ensure software quality.
 Purpose:
• Detect defects early.
Deliver a high-quality product.
• Key Phases:
• 1. Requirement Analysis.
• 2. Test Planning.
• 3. Test Case Design.
• 4. Test Environment Setup.
• 5. Test Execution.
• 6. Test Closure.
 Phase 1 - Requirement Analysis
• Objective:
• Understand what needs to be tested.
• Activities:
• Analyze functional and non-functional requirements.
• Identify testing priorities.
• Define acceptance criteria.
• Outcome:
• Requirement Traceability Matrix (RTM).
 Test Planning
• Objective:
• Develop a roadmap for testing activities.
• Activities:
• Create a test plan document.
• Allocate resources and tools.
• Define test metrics and criteria.
• Outcome:
• Test Plan Document.
• Resource Allocation.
 Test Case Design
• Objective:
• Write detailed test cases for execution.
• Activities:
• Identify test scenarios.
• Design test cases and test scripts.
• Prioritize test cases based on risk.
• Outcome:
• Test Case Document.
 Test Environment Setup
• Objective:
• Prepare the testing environment.
• Activities:
• Configure hardware and software.
• Prepare test data.
• Verify environment readiness.
• Outcome:
• Ready-to-use test environment.
 Test Execution
• Objective:
• Execute test cases and report defects.
• Activities:
• Run manual or automated test cases.
• Log defects in a tracking tool.
• Retest and close fixed defects.
• Outcome:
• Defect Reports.
• Test Results.
 Test Closure
• Objective:
• Wrap up the testing process.
• Activities:
• Analyze test metrics.
• Document lessons learned.
• Archive test artifacts.
• Outcome:
• Test Closure Report.
 testing scope
• Introduction to Testing Scope
• Definition:
• The boundaries and extent of testing activities for a
software project.
 Purpose:
• Define what will be tested and what will not.
• Ensure resources focus on critical areas.
• Key Question:
• What needs to be tested to meet the requirements?
 Importance of Defining Scope
• Why Define Scope?
• Avoids over-testing or missing critical areas.
• Ensures efficient use of time and resources.
• Aligns testing efforts with project goals.
• Consequences of Poor Scope Definition:
Increased costs.
• Missed deadlines.
• Overlooked defects.
 Types of Testing Scopes
• Unit Testing:
• Focus: Testing individual components or modules.
• Example: Testing a login button’s functionality.
• 2. Integration Testing:
• Focus: Testing interactions between modules.
• Example: Data flow between login and dashboard.
• System Testing:
• Focus: Testing the entire application as a whole.
• Example: End-to-end testing of an e-commerce website.
• 4.Acceptance Testing:
• Focus: Verifying that the product meets user requirements.
• Example: Final validation before deployment.
 Factors Affecting Testing Scope
• Project Requirements:
• Functional and non-functional goals.
• Available Resources: Time, tools, and personnel.
• Project Risks: High-risk areas get more focus.
• Budget Constraints: Testing scope aligns with financial
resources.
 Managing Testing Scope
• Steps to Manage Scope:
• 1Define critical functionalities.
• 2.Prioritize testing based on risk and impact.
• 3.Communicate scope clearly with stakeholders.
• 4.Monitor and adjust scope as requirements evolve.
• Tools: Use Requirement Traceability Matrix (RTM) to
track scope.