Scribd
Upload
6 views

Manual Testing Basics-01 Module

Manual Testing is the process of manually executing test cases to identify defects in software applications, ensuring they meet functional and user experience requirements. It is important for detecting usability issues, exploratory testing, and is cost-effective for small projects. The Manual Testing Process includes steps such as requirement analysis, test planning, test case development, and defect reporting, with various types of testing like black box, white box, and regression testing.

Uploaded by

BENSALAH ines
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
6 views

Manual Testing Basics-01 Module

Manual Testing is the process of manually executing test cases to identify defects in software applications, ensuring they meet functional and user experience requirements. It is important for detecting usability issues, exploratory testing, and is cost-effective for small projects. The Manual Testing Process includes steps such as requirement analysis, test planning, test case development, and defect reporting, with various types of testing like black box, white box, and regression testing.

Uploaded by

BENSALAH ines
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Manual Testing

Basic (Part-01)

Author:Shubham Latake
What is Manual Testing ?

Definition:
Manual Testing is the process of manually executing test cases without using automation
tools to find defects in a software application.

Key Features:
➔ Performed by human testers.
➔ Ensures software meets functional and user experience requirements.
➔ Detects UI, usability, and logical errors.

Author:Shubham Latake
Why Manual Testing is important ?

Manual Testing is important because:

➔ It helps identify usability issues that automation cannot detect.


➔ It is essential for exploratory, ad-hoc, and user experience testing.
➔ It is cost-effective for small projects.
➔ It allows human intuition and creativity in test execution.

Author:Shubham Latake
Manual Testing Process :

1⃣ Requirement Analysis –Understand project needs and identify functionality

2⃣ Test Planning – Define scope, objectives, and assign tester roles.

3⃣ Test Case Development – Write and review detailed test cases.

4⃣ Test Environment Setup – Prepare hardware, software, and test data.

5⃣ Test Execution – Run test cases, compare results, and report defects.

6⃣ Defect Reporting & Tracking – Log, track, and retest bugs after fixes.

7⃣ Test Closure – Finalize testing, document results, and share reports.

Author:Shubham Latake
Types of Manual Testing
1. Black Box Testing – Tests functionality without knowing internal code
(e.g., verifying login feature works).

2.White Box Testing – Tests internal logic and code structure


(e.g., checking loops and conditions in a program).

3. Gray Box Testing – Combines Black & White Box Testing


(e.g.testing a database-driven web application with partial knowledge of code).

4. Acceptance Testing – Ensures software meets business needs before release


(e.g.client verify an e-commerce website before launch)

5. System Testing – Tests the entire system as a whole


(e.g., checking if an online banking system works end-to-end).

6. Integration Testing – Tests interactions between modules


(e.g., verifying data flows correctly between login and dashboard).
Author:Shubham Latake
Types of Manual Testing
7. Unit Testing – Tests individual components or functions
(e.g., testing a "Calculate Total Price" function in a shopping cart) .

8. Sanity Testing – Quick check to verify basic functionality after small changes
(e.g., ensuring login works after updating the UI).

9. Smoke Testing – Basic tests to check system stability before deeper testing
(e.g., ensuring critical features work after a new build).

10. Regression Testing – after changes to ensure nothing breaks


(e.g.verifying checkout still works after adding a discount feature).

11.UI Testing – Verifies design, layout, and user experience


(e.g., checking if buttons, fonts, and colors are displayed correctly).

12. Exploratory Testing – Unscripted testing to find unexpected issues


(e.g., randomly navigating an app to uncover hidden bugs).
Author:Shubham Latake
Software Testing Life Cycle (STLC) :
1⃣ Requirement Analysis :

✅ Understand business and functional requirements.


✅ Identify testable features and clarify doubts with stakeholders.
🔹 Example: Checking if login functionality requires multi-factor authentication.

2⃣ Test Planning :

✅ Define test objectives, scope, schedule, and resources.


✅ Select testing tools and assign roles to testers.
🔹 Example: Deciding to use Jira for bug tracking and allocating testers for functional testing.

3⃣ Test Case Development :

✅ Write detailed test cases with input, steps, and expected results.
✅ Prepare test data and review cases before execution.
🔹 Example: Writing a test case for login: Enter valid username & password → Click Login → User should be
redirected to the homepage.

Author:Shubham Latake
Software Testing Life Cycle (STLC) :
4⃣ Test Environment Setup :

✅ Configure hardware, software, and network for testing.


✅ Ensure test data and access permissions are ready.
🔹 Example: Setting up a test server for an e-commerce application to simulate real-world usage.

5⃣ Test Execution :

✅ Execute test cases manually or using automation tools.


✅ Compare actual vs. expected results, log defects, and retest fixes.
🔹 Example: Running a test for the checkout process and reporting a bug if payment fails.

6⃣ Test Closure :

✅ Prepare test summary reports and analyze defect trends.


✅ Ensure all critical bugs are fixed and document lessons learned.
🔹 Example: Creating a final report with defect counts, test coverage, and improvement areas.

Author:Shubham Latake
Follow for more information…..

Shubham Latake

You might also like