Manual Testing Q/A

1. What is Manual Testing?
   Manual testing is the process of manually executing test cases without using automation tools to identify bugs and ensure the software functions as expected.

2. What is the difference between Manual Testing and Automation Testing?

   • Manual Testing requires human effort to execute test cases, while Automation Testing uses scripts and tools.

   • Manual Testing is slower compared to Automation Testing.

   • Automation Testing is useful for repetitive tasks like regression testing, whereas Manual Testing is better for usability and exploratory testing.

3. What are the different types of Manual Testing?

   • Functional Testing

   • Usability Testing

   • Smoke Testing

   • Regression Testing

   • Exploratory Testing

   • Ad-hoc Testing

4. What are Test Cases?
   A test case is a set of conditions and steps used to verify if a software application functions correctly.

   Example:

   • Step 1: Open the login page

   • Step 2: Enter valid username and password

   • Step 3: Click the "Login" button

   • Expected Result: User should be logged in successfully

5. How would you test a login page manually?

   • Check login with valid and invalid credentials.

   • Verify "Forgot Password" functionality.

   • Check UI elements such as buttons and fields.

   • Test session timeout and security aspects.

6. What is Regression Testing?
   Regression testing ensures that recent code changes do not break existing functionalities.

7. What is the difference between Smoke and Sanity Testing?

   • Smoke Testing checks major functionalities of the application to ensure basic stability.

   • Sanity Testing verifies specific bug fixes or new features to confirm they work as expected.

8. What is Exploratory Testing?

   Exploratory testing is performed without predefined test cases, allowing testers to explore the application and find unexpected defects.

9. What are Severity and Priority in Bug Tracking?

   • Severity refers to the impact of the bug on the system (Critical, High, Medium, Low).

   • Priority refers to the urgency of fixing the bug (High, Medium, Low).

     Example:

     High Severity, Low Priority: A crash in an admin-only feature.

     Low Severity, High Priority: A spelling mistake on the homepage title.

10. Which bug tracking tools have you used?

    • JIRA

    • Bugzilla

    • Trello

11. What are the different levels of testing?

    • Unit Testing

    • Integration Testing

    • System Testing

    • User Acceptance Testing (UAT)

12. What is the difference between White Box and Black Box Testing?

    White Box Testing checks internal code and logic (done by developers), while Black Box Testing tests functionality without knowing internal code (done by testers).

13. What is a Test Plan and what does it include?

    A Test Plan is a document that outlines the testing scope, objectives, schedule, resources, and deliverables. It includes:

    • Test strategy

    • Test scope

    • Testing schedule

    • Test environment details

    • Test deliverables

14. What is a Test Scenario?
    A test scenario is a high-level description of a functionality to be tested.

15. What is the difference between a Test Case and a Test Script?
    A test case is a step-by-step document to verify a feature, while a test script is a set of automation instructions written for testing tools.

16. What is the Defect Life Cycle (Bug Life Cycle)?

    The defect life cycle includes the following stages:

    • New → Assigned → Open → Fixed → Retested → Verified → Closed

17. What are different types of defects?

    • Functional Defects

    • Performance Defects

    • Security Defects

    • Compatibility Defects

    • UI Defects

18. How do you report a bug?

    A bug should be reported with:

    • Summary

    • Steps to reproduce

    • Expected vs actual results

    • Screenshots/logs

    • Priority and severity

19. How would you test a login page manually?

    • Check login with valid and invalid credentials

    • Verify "Forgot Password" functionality

    • Check UI elements such as buttons and fields

    • Test session timeout and security aspects

15. What is Regression Testing?
    Regression testing ensures that recent code changes do not break existing functionalities.

16. What is the difference between Smoke and Sanity Testing?

    • Smoke Testing checks major functionalities of the application to ensure basic stability.

    • Sanity Testing verifies specific bug fixes or new features to confirm they work as expected.

17. What are Severity and Priority in Bug Tracking?

    • Severity refers to the impact of the bug on the system (Critical, High, Medium, Low).

    • Priority refers to the urgency of fixing the bug (High, Medium, Low).

      Example:

    • High Severity, Low Priority: A crash in an admin-only feature.

    • Low Severity, High Priority: A spelling mistake on the homepage title.

18. What is Exploratory Testing?
    Exploratory testing is performed without predefined test cases, allowing testers to explore the application and find unexpected defects.

19. How would you test an e-commerce website?

    • Verify user login and signup functionality

    • Test product search and filtering

    • Check the checkout and payment process

    • Validate order tracking and cancellation

    • Perform UI and security testing

21. How do you handle a situation where a developer does not accept a reported defect?

    • Reproduce the bug and provide clear evidence (screenshots, logs)

    • Explain the impact of the defect

    • Discuss with the test lead or business analyst if required

22. What would you do if you find a critical bug just before release?

    • Immediately report it to the test lead and stakeholders

    • Assess the impact and severity

    • Suggest a fix or a workaround

    • Document the risk if the fix is postponed

23. How do you perform cross-browser testing manually?

    • Open the application in different browsers (Chrome, Firefox, Edge, Safari)

    • Check UI consistency and responsiveness

    • Validate functionality in each browser

24. What is Compatibility Testing?
    Compatibility testing ensures that the software works across different devices, browsers, operating systems, and network environments.

25. What are the key qualities of a good software tester?

    • Analytical skills

    • Attention to detail

    • Communication skills

    • Curiosity and exploratory mindset

    • Problem-solving ability

26. What is Risk-Based Testing?
    Risk-based testing prioritizes test cases based on the likelihood and impact of failure.

27. What is the difference between Static Testing and Dynamic Testing?

    • Static Testing involves reviewing documents, code, and requirements without execution.

    • Dynamic Testing involves executing the software to identify defects.

28. What is Boundary Value Analysis (BVA)?
    BVA is a test design technique where test cases are created for boundary values of input fields.

Example:
If an input field accepts values from 1 to 100, test cases should include 0, 1, 100, and 101.

29. What is Equivalence Partitioning?
    Equivalence Partitioning is a technique where input data is divided into valid and invalid partitions, and test cases are created for each partition.

30. What is Use Case Testing?
    Use case testing validates the application from an end-user perspective by testing real-world scenarios.