Manual Testing and Automation Testing Presentation

1. Manual Testing
&
Automation Testing
S O F T WA R E T E S T I N G
P R E S E N TAT I O N
Present By:
Abishek Immanuel - 24MX201
Boopathirajan - 24MX205

2. Manual Testing

3. MANUAL TESTING
• Manual Testing is the process of testing
software manually to find defects.
• The tester plays the role of an end-user
and verifies all features to ensure the
application behaves as expected.

4. CHARACTERISTICS OF MANUAL TESTING
• Human involvement: Testers use their intuition and experience.
• Documentation-based: Requires test plans, test cases, bug
reports.
• Dynamic process: You adapt as you test

5. TYPES OF MANUAL TESTING
• Smoke Testing - Basic testing to verify major functions work.
• Sanity Testing - Narrow testing to check a specific feature.
• Regression Testing - Ensures old functionalities work after changes.
• Exploratory Testing - No test cases; tester explores freely.
• Usability Testing - Checks how user-friendly the app is.
• Acceptance Testing - Ensures the app meets business needs (UAT).

6. ADVANTAGES
• Good for UI testing: The Human eye catches layout/design
issues.
• Flexible: Easily adapts to change.
• Cost-effective for small projects: No tool/setup needed.
• Real-time feedback: Testers can suggest improvements instantly.

7. DISADVANTAGES
• Time-consuming: Repeating tests for every update takes time.
• Less reliable: Prone to human error and oversight.
• Not scalable: Can’t run thousands of tests quickly like
automation.
• Repetitive work: Regression tests can be boring.

8. TOOLS USED TO SUPPORT MANUAL TESTING
TEST CASE MANAGEMENT –
BUG TRACKING –

9. CASE STUDY
Manual Testing of Shopping
Cart
• Objective:
To test the Shopping Cart functionality of an online store to
ensure users can add, view, update, and remove items correctly before
proceeding to checkout.

10. CASE STUDY
Manual Testing of Shopping
Cart
• Requirements:
⚬ Users can add one or more items to the cart.
⚬ Users can view cart summary with item name, quantity, price, and
total.
⚬ Users can increase/decrease quantity or remove items.

11. Test Case Table

12. CASE STUDY
Manual Testing of Shopping
Cart
We are using the TestRail tool to demonstrate how test cases are
managed
<Demo shown on the laptop>
TestRail is a web-based test case management tool. It is used by
QA engineers, developers, and team leads to manage, track, and
organize software testing efforts.

13. Automation
Testing

14. AUTOMATION TESTING
• Automation Testing is a software testing
technique that performs using special
automated testing software tools to execute a
test case suite.
• The software can also enter test data into the
System Under Test, compare expected and
actual results and generate detailed test
reports.

15. AUTOMATION TESTING
• Successive development cycles will require
execution of same test suite repeatedly. Using
a test automation tool, it’s possible to record
this test suite and re-play it as required.
• Once the test suite is automated, no human
intervention is required. This improves ROI of
Test Automation.

16. WHY
AUTOMATION
TESTING?
The goal of Automation is to reduce the
number of test cases to be run manually and
not to eliminate Manual Testing altogether.
Test Automation is the best way to
increase the effectiveness, test coverage,
and execution speed in software testing.
• Manual Testing of all workflows, all fields, all
negative scenarios is time and money
consuming.
• It is difficult to test for multilingual sites
manually
• Test Automation in software testing does not
require Human intervention. You can run
automated test unattended (overnight)

17. High Risk - Business
Critical test cases
WHAT TYPE OF TEST CASES CAN BE AUTOMATED?
Test cases that are
repeatedly executed
Test cases that are
tedious or difficult to
perform manually
Test cases which are
time consuming
Payment gateway
functionality,Login
and authentication
User Registration
form validation,Add
to cart/checkout
process
FIlling out 10-step multi-
page form
Testing combinations of
user roles and
permissions
Running tests across
multiple browsers and
devices
Bulk data import and
validation tests

18. AUTOMATION TESTING PROCESS

19. WHAT IS A TEST AUTOMATION FRAMEWORK?
A test automation framework is a set of guidelines that help
organize and structure automated testing effectively.
Benefits:
• Ensures consistency in test design and execution
• Promotes reusability and modularity of code
• Reduces maintenance effort
• Allows partial involvement of non-technical testers
• Simplifies onboarding and reduces training time
• Enables easy integration of test data (e.g., data-driven
testing)

20. TYPES OF AUTOMATION FRAMEWORKS

21. TYPES OF AUTOMATION FRAMEWORKS
Test data is separated from the test script and stored externally (e.g., Excel, CSV,
database).
Allows the same script to run multiple times with different input values.
DATA DRIVEN FRAMEWORK
KEYWORD DRIVEN
FRAMEWORK
Uses keywords (like Click, EnterText, Verify) to define actions in external files (e.g.,
Excel)
Enables non-programmers to write test steps using predefined keywords.
MODULAR AUTOMATION FRAMEWORK
Breaks down the application under test into smaller, independent
modules and writes scripts for each.
Promotes code reusability and easier maintenance.
HYBRID AUTOMATION FRAMEWORK
A combination of two or more frameworks
(commonly Data-Driven + Keyword-Driven +
Modular).

22. BENEFITS OF AUTOMATION
TESTING
• Faster Execution - Automates repetitive tasks and runs tests much
faster than manual testing.
• Increased Test Coverage - More tests can be run across different
devices, browsers, and data sets.
• Improved Accuracy - Eliminates human error in repetitive test
cases.
• Reusability of Test Scripts - Once written, test scripts can be
reused for multiple test cycles.
• Supports Continuous Integration - Easily integrates with CI/CD
pipelines (e.g., Jenkins, GitHub Actions).
• Better Reporting - Automated tests can generate detailed logs
and reports for analysis.

23. DISADVANTAGES OF AUTOMATION TESTING
• High Initial Investment - Setting up tools, frameworks, and
writing scripts can be time-consuming and costly.
• Not Suitable for All Test Cases - Exploratory, usability, and ad-hoc
testing still require manual effort.
• Requires Technical Skills - Creating and maintaining test scripts
often needs programming knowledge.
• Maintenance Overhead - Scripts may break when the UI or logic
changes frequently, requiring regular updates.
• Limited Flexibility - Automation cannot easily handle unexpected
behavior or complex real-user interactions.

24. POPULAR AUTOMATION TESTING TOOLS
WEB AND UI
TESTING
MOBILE APP TESTING

25. POPULAR AUTOMATION TESTING
TOOLS
API TESTING
UNIT TESTING
FRAMEWORKS

26. POPULAR AUTOMATION TESTING
TOOLS
CI/CD AND INTEGRATION

27. REFERENCES
• Software Testing: Principles and Practices – Srinivasan Desikan,
Gopalaswamy Ramesh
• ISTQB Official Site -Certification guide and glossary of testing terms
• TestRail - Test cases Management Documentation
• Experiences of Test Automation – Dorothy Graham, Mark Fewster
• Selenium Official Website - Best for Selenium WebDriver and Grid
documentation.
Manual Testing
Automation Testing

28. THANK YOU
Questions?