Summary of "Complete Manual Testing Course: Learn Testing from Scratch"

1. Introduction to Software Testing

Software testing is the process of verifying that software works as expected and meets customer requirements.
Testing aims to find defects (bugs) and improve software quality.
Testing applies to all software development models and is mandatory in every project.
Two main types of testing:
- Manual Testing: Human testers perform test steps without automation tools.
- Automation Testing: Tests executed automatically using tools like Selenium, UFT, Katalon Studio, etc.
The course covers all fundamentals from scratch, suitable for beginners and experienced professionals.

SDLC is a systematic process to develop software, including phases:
- System Investigation
- Requirement Analysis
- Design (High-Level and Low-Level)
- Coding/Implementation
- Testing
- Release & Maintenance
Various stakeholders involved: Business Analyst (BA), Project Manager, Architect, Developers, Testers, Release Engineers, Support, Finance, HR.
Different documents created during SDLC: BRD (Business Requirement Document), FRD (Functional Requirement Document), SRS (Software Requirement Specification).
Testing is an integral part of SDLC.

STLC phases:
- Requirement Analysis
- Test Planning
- Test Case Design
- Test Execution
- Defect Reporting & Tracking
- Test Closure
Defect Life Cycle is a sub-process within STLC.
Traceability Matrix (RTM) maps requirements to test cases and defects to ensure coverage.

Waterfall Model: Linear sequential phases, no going back once a phase is completed; suitable for small, stable projects.
Iterative Model: Development in repeated cycles (iterations), delivering working software incrementally.
Spiral Model: Combines Waterfall and Iterative with strong risk analysis; suitable for large, complex projects.
V-Model: Extension of Waterfall with corresponding testing phases for each development phase; emphasizes verification and validation.
Agile Model: Iterative and incremental development with frequent delivery, flexible to requirement changes, uses Sprints and Scrum framework.
Scaled Agile Framework (SAFe): Agile implementation at enterprise level with portfolio, program, and team layers.
Prototype Model: Build a prototype based on unclear or new requirements, refine with customer feedback before full development.
Hybrid Model: Combination of two or more models tailored to project needs.
Derived Model: Customized models derived from base models like Waterfall (e.g., Spiral, V-Model).

Manual Testing involves testers acting as end users to verify features and find defects.
Types of Manual Testing include Unit, Integration, System, and Acceptance Testing.
Test case design techniques include boundary value analysis, equivalence partitioning, decision tables, state transition, and error guessing.
Common misconceptions about Manual Testing:
- Not everyone can do Manual Testing without knowledge.
- Testing is not just UI verification.
- Testing cannot guarantee 100% defect-free software.
- Automation is not always more powerful than Manual Testing.
- Manual Testing is not non-technical or easy.

Verification: Are we building the product right? (Checking documents, requirements, design, code) — static testing.
Validation: Are we building the right product? (Actual testing of the product) — dynamic testing.
Verification corresponds to Quality Assurance (QA), Validation corresponds to Quality Control (QC).

QA: Process-oriented, preventive, focuses on improving SDLC, involves planning, monitoring, and process improvement.
QC: Product-oriented, corrective, focuses on testing the actual product, involves testers executing test cases and reporting defects.

Test Plan: Project-level document detailing scope, objectives, schedule, resources, approach, deliverables, risks, and approvals.
Test Strategy: Organization-level document outlining the overall approach, methodologies, standards, and guidelines for testing.
Test planning is done by test leads/managers; test strategy by project managers or organizational quality teams.

Test Scenario: High-level functionality to be tested (e.g., Login functionality).
Test Case: Detailed steps with inputs, expected results, preconditions, postconditions, and status.
Importance of writing clear, concise, maintainable test cases linked to requirements.