Manual Testing Complete Course

(Beginner to Advanced)

Author: Mr. Amol Chavhan

1
 Module 1: Introduction to Testing
Topics:

• What is Software Testing?

• Why is Testing Important?
• Types of Testing: Manual vs. Automation
• SDLC vs. STLC (Software Development Life Cycle vs. Software Testing Life Cycle)
• QA vs QC (Quality Assurance vs Quality Control)

Explanation:

Software Testing is the process of checking if a software application works correctly and
meets user expectations. It helps in finding and fixing errors or bugs before the software is
used by real users.

Manual Testing means testing the software by a human tester, without using any automation
tools.

Automation Testing uses special tools or scripts to test the software automatically.

QA (Quality Assurance) is about improving processes to prevent defects.

QC (Quality Control) is about checking the final product to find defects.

SDLC is the process of developing software.

STLC is the process of testing the software.

Real-Life Example:

Imagine you're buying a new mobile phone. Before paying, you:

• Check the screen

• Test the camera
• Listen to the speaker
• Try opening apps

This is similar to manual testing. You’re making sure everything works fine manually.

Quiz:

1. What is the main difference between QA and QC?

2. Give two examples of manual testing from daily life.

Flashcards:

• QA: Process-oriented, focuses on preventing defects.

• QC: Product-oriented, focuses on finding defects.

2
 • Manual Testing: Human tester checks the software.
• Automation Testing: Tool/script checks the software.

Module 2: Types of Software Testing

Topics:

• Functional Testing
• Non-functional Testing
• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing
• Regression Testing
• Smoke and Sanity Testing

Explanation:

Functional Testing checks if the application does what it's supposed to do.
Non-functional Testing checks how well the application works (speed, security, etc.).

Unit Testing is done by developers to test individual parts of the code.

Integration Testing checks if different modules work together.
System Testing is testing the whole application as a single system.
Acceptance Testing is done by the customer to confirm the product meets their needs.
Regression Testing checks that new changes haven’t broken existing features.
Smoke Testing is a basic test to see if the main features work.
Sanity Testing checks small parts of the app after changes.

Real-Life Example:

ATM machine:

• Functional Testing: Entering PIN, withdrawing money.

• Non-functional Testing: How fast the ATM responds.

Quiz:

1. What is Regression Testing?

2. What is the difference between Functional and Non-functional Testing?

Flashcards:

• System Testing: Tests the complete application.

• Acceptance Testing: Done by the user/client.
• Smoke Test: Initial quick check.
• Sanity Test: Checks a specific functionality after a change.
3
 Module 3: Software Development Life Cycle (SDLC)
Topics:

• SDLC Phases: Requirement, Design, Implementation, Testing, Deployment,

Maintenance
• Waterfall Model
• Agile Model
• V-Model

Explanation:

SDLC is a step-by-step approach to building software. Each phase helps in creating a reliable
product.

• Requirement Phase: Understand what the user wants.

• Design Phase: Plan how to build the system.
• Implementation (Coding): Write the code.
• Testing: Test the system.
• Deployment: Launch the system.
• Maintenance: Fix issues after launch.

Real-Life Example:

Planning a birthday party:

• You gather ideas (Requirement),

• Plan decoration and food (Design),
• Set up the venue (Implementation),
• Test lights, sound, food (Testing),
• Host the party (Deployment),
• Clean up and fix issues (Maintenance).

Quiz:

1. Name three phases of SDLC.

2. In which SDLC phase do we perform testing?

Flashcards:

• Agile: A flexible, fast way to develop software in small parts.

• Waterfall: Step-by-step development model.
• V-Model: Each development step has a related testing step.

4
 Module 4: Software Testing Life Cycle (STLC)
Topics:

• Requirement Analysis
• Test Planning
• Test Case Development
• Environment Setup
• Test Execution
• Test Closure

Explanation:

STLC is the series of steps followed to test software systematically. It ensures no part of
testing is missed.

1. Requirement Analysis – Understand what needs to be tested.

2. Test Planning – Define strategy, resources, and timeline.
3. Test Case Development – Write steps to test each function.
4. Environment Setup – Prepare systems needed for testing.
5. Test Execution – Run test cases and record results.
6. Test Closure – Review and share what was tested and results.

Real-Life Example:

Before going on a road trip:

• Check your car documents (Analysis),

• Make a checklist of items (Planning),
• Pack your items (Test Cases),
• Get your car serviced (Environment),
• Go on the trip and check checklist (Execution),
• Return and review the trip (Closure).

Quiz:

1. What is the first step of STLC?

2. Why is test closure important?

Flashcards:

• Test Planning: Planning resources and strategy.

• Test Execution: Running and recording test results.

5
✅ Module 5: Test Case Design Techniques
Topics:

• What is a Test Case?

• Test Scenario vs Test Case
• Writing Effective Test Cases
• Test Data Creation
• Boundary Value Analysis
• Equivalence Partitioning
• Decision Table Testing

Explanation:

A Test Case is a set of conditions or steps used to test a specific part of an application to
check if it works correctly.

Test Scenario is a high-level idea of what to test.

Test Case is a detailed document of how to test that scenario.

Techniques:

• Boundary Value Analysis (BVA): Test values at the edge/boundaries. Example: For
age input between 18–60, test 17, 18, 60, 61.
• Equivalence Partitioning (EP): Divide data into valid and invalid partitions.
Example: For valid age = 18–60, test one value from each group (like 25, 10, 70).
• Decision Table: Test based on different input combinations and expected outputs.

Quiz:

1. What is the difference between a test scenario and a test case?

2. Give an example of Boundary Value Analysis.

Flashcards:

• Test Case: Step-by-step testing method.

• Test Scenario: High-level idea to test.
• BVA: Tests at boundary limits.
• EP: Divide input into valid/invalid groups.

Module 6: Test Management Tools

Topics:

• Test Case Management using Excel/Sheets

• Introduction to JIRA

6
 • TestLink (Open-source test tool)
• Bug Reporting
• Test Cycle Creation

Explanation:

Test Management Tools help testers to organize, track, and manage test cases and bugs
efficiently.

Excel: Best for beginners to write and manage test cases. JIRA: A widely used tool to track
bugs, tasks, and test progress. TestLink: Open-source platform for managing test cases.

Real-Life Example:

Like creating a to-do list and marking tasks done – you do the same with test cases in Excel
or tools like JIRA.

Quiz:

1. Name one open-source test management tool.

2. What is JIRA used for?

Flashcards:

• JIRA: Bug and task tracking tool.

• TestLink: Tool to write and manage test cases.
• Excel: Simple tool for test case management.

Module 7: Defect/Bug Life Cycle

Topics:

• What is a Defect/Bug?
• Bug Life Cycle
• Severity vs Priority
• Defect Report Format

Explanation:

A bug is an error in the software that causes incorrect results or behavior.

Bug Life Cycle:

• New → Assigned → Open → Fixed → Retest → Closed (or Reopened)

7
Severity = How serious the bug is.
Priority = How soon it should be fixed.

Real-Life Example:

If your room's light switch doesn't work:

• New: You report the issue.

• Assigned: Electrician is assigned.
• Fixed: Issue is repaired.
• Retest: You test the switch.
• Closed: It works fine now.

Quiz:

1. What is the difference between severity and priority?

2. What are the key stages of a bug life cycle?

Flashcards:

• Severity: Impact of defect.

• Priority: Urgency of fixing.
• Bug: An issue in the software.

Module 8: Web and Mobile Application Testing

Topics:

• Web Application Testing

• Mobile App Testing Basics
• Responsive Testing
• Cross-browser Testing
• Usability Testing

Explanation:

Web Testing involves testing websites on different browsers and devices. Mobile App
Testing checks mobile apps on Android/iOS. Responsive Testing ensures the app layout
adapts to screen sizes. Usability Testing ensures the app is user-friendly.

Real-Life Example:

Using Flipkart on a computer and a phone – the layout should look good and work well on
both.

Quiz:

8
 1. What is responsive testing?
2. What is usability testing?

Flashcards:

• Responsive: Adjusts layout for screen size.

• Usability: Easy to use.

Module 9: Real-Time Project Practice

Practice Projects:

1. Banking App – Login, Fund Transfer, Balance Check

2. E-commerce Site – Search, Add to Cart, Checkout
3. Food Delivery App – Search, Order, Track Delivery

Tasks:

• Write Test Cases

• Execute Tests
• Report Bugs
• Share Test Summary

Quiz:

1. What would you test in a payment gateway?

2. What’s one negative test case for a login page?

Module 10: Interview Preparation

Topics:

• Most Asked Interview Questions

• How to Explain Your Project
• Resume Tips
• Scenario-Based Questions

Example Interview Questions:

• What is the difference between verification and validation?

• How do you log a bug?
• Describe your role in your last project.

9
Tips:

• Be confident and clear

• Use real project examples
• Practice mock interviews

10