Top Manual Testing Interview Questions and Answers – Part 1 (2025 Updated)

1. Authentication and authorization?

• Authentication (Auth): Verifies the user's identity.
• Authorization: Determines the user's permissions.Defines what actions the user can perform.

   
2. Retesting and Regression testing?

• Retesting involves testing a specific bug or issue after it has been fixed by the developer.
•  Regression testing involves testing the fixed bug and the surrounding areas that may have been affected by the fix. verify that the software works as expected after changes?

  Retesting - Testing only the affected area.
  Regression Testing - Testing the affected as well as the unaffected areas.
  
3. Black Box, White Box, Gray Box Testing:

•  Black box: Focuses on external behaviour and user interactions. No knowledge of internal code or structure required. Typically performed by testers, QA engineers, or end-users. Examples: Functional testing, User Acceptance Testing (UAT), Exploratory testing.
• White Box: Focuses on internal code structure and logic. Requires knowledge of programming languages and code. Typically performed by developers. Examples: Unit testing, Integration testing, Code reviews.
• Gray Box: Combines elements of black box and white box testing. Requires some knowledge of programming and code. Typically performed by testers with programming skills or developers. Examples: API testing, Database testing, Security testing.

  
4. Severity: Refers to the impact or effect of a defect on the application's functionality. Measures the defect's damage or risk
     Priority: How soon will the defect be fixed?
  
5. Test scenarios focus on what to test, while test cases focus on how to test. Test scenarios define end-to-end functions to be tested, while test cases provide instructions on how to test specific features.

6. Alpha, Beta, Gamma Testing:
  Alpha: Conducted by the in-house testing team. Focus on functionality.
  Beta: Conducted by external customers, end-users, or a select group. Focus on real-world usage.
  Gamma: Conducted by end-users and customers. For the final validation, focus on business requirements and user expectations.
  
7. Equivalence Partitioning:

• Equivalence partitioning is a black-box testing technique that divides input data into partitions.
• Test cases that cover all possible input scenarios reduce the number of test cases.

 Example:  Age (1-100)
   Valid ages: 1-100
   Invalid Ages:
       Below 1 (e.g., 0, -1)
       Above 100 (e.g., 101, 150)
       Non-numeric input (e.g., "abc")

8. Smoke and Sanity testing

• Smoke testing - Focusing on Major functionalities in the software through positive test cases.
• Sanity testing - Focusing on Major functionalities in the software through positive and negative test cases.

9. Usability testing - Easy to use.

10. BUG - Caused by a programming error.
      ERROR - Mismatch between expected and actual output.
      DEFECT - When the actual output differs from customer expectations, it is considered a defect.
      MISTAKE - An error made by the user.

11. Adhoc/Monkey testing - testing an application randomly without following the requirements. Here we check negative scenarios.

12. Compatibility testing - testing an application with different hardware and software.

13. Globalisation testing - testing an application which is developed for different languages.

14. Reliability testing - testing the functionality of an application for a long duration of time.

15. Accessibility testing - testing the application which is developed for physically challenged people.

16. Acceptance testing - testing the business scenarios of an application, which is done by the customer.

17. Aesthetic testing - Testing the beauty of the application. checking colour combination, font style, font size and attractiveness of an application.

18. Functional, integration and system testing are mandatory for every testing application.

19. Smoke, sanity, exploratory and ad-hoc testing are situation-based testing.

20. Recovery testing - Later, close the application and open it again, and see whether all the previous data is still available or not.

21. SDLC - It is the Software Development Life Cycle

 It has different stages:

• Requirement Analysis
• Designing
• Coding
• Testing
• Deployment
• Maintenance

22. Agile Model - When a customer wants an application very fast, with less time, we go for this model.

23. STLC - Software Testing Life Cycle

  It has different stages:

• Requirement Analysis
• Test Planing
• Test Designing
• Test Environment Setup
• Test execution
• Test Cycle Closure

24. Scrum terminology

Scrum is a version of agile.

• Epic - It is a complete set of requirements given by the customer.
• Sprint - It is the duration of time taken to work on 1 or more user stories. Each sprint can be either 2/3/4 weeks, depending on the customer's decision.
• Sprint planning meeting - It is a meeting which is conducted before the sprint starts.
• Sprint backlog - It is a user story which is not completed in that particular sprint and is carried into the next sprint.
• Sprint review meeting - In this meeting, the scrum master will check whether all the user stories are completely developed and tested, and it is ready to be released to the customer or not.

25. Requirement Traceability Matrix:

• It is a document which is prepared to check whether every requirement has at least one test case or not. RTM maps all the requirements with the test cases.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Open to Work – Software Test Engineer Seeking Opportunities (Manual & Automation)

Hi everyone! I’m actively seeking a new opportunity and would appreciate your support. If you have any relevant openings or would like to connect, please message me or comment below.

🔹 Open to New Roles | Software Test Engineer 🔹

I am a Senior Software Test Engineer (Automation and Manual) with 4+ years of experience in testing web-based applications. My expertise includes:
✅ Automation Testing – Java, Selenium WebDriver, TestNG
✅ API Automation – Rest-Assured, Postman
✅ Manual Testing – Comprehensive test planning, execution, and defect reporting
✅ Team Collaboration – Leading QA teams, mentoring, and training new members
✅ Bug Identification & Documentation – Proficient in tracking and reporting software issues

💻 Technical Skills & Tools:

🔹 Languages – Java | SQL
🔹 API Testing Tools – Postman
🔹 Automation Testing – Selenium WebDriver | TestNG | Java | Maven | WebdriverIO | Appium | Android Studio
🔹 Performance Testing – JMeter
🔹 Database – MySQL | Oracle
🔹 Test Management Tools – Jira | Asana
🔹 CI/CD Pipelines – GitHub Actions
🔹 Domain Expertise – ERP | EdTech | CRM | E-commerce | Healthcare

Contact Info:

📌 QA Blog – https://suriyaparithy.blogspot.com/
📌 GitHub – https://github.com/parithysuriya
📌 Portfolio – https://suriyaparithy.wixsite.com/suriyae
📌 LinkedIn – https://www.linkedin.com/in/suriya-e-211681148/

📍 Preferred Locations:

🏢 On-Site: Madurai | Coimbatore | Chennai
🏡 Remote: India

Feel free to connect or reach out for opportunities!
📩 Email – suriyaparithy@gmail.com
📞 Phone – +91 8344418512

---

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Easy Steps to Navigate Any Website Like a Pro – Beginner’s Guide

Manually exploring a site involves checking its various features, functionality, and usability. Here's a comprehensive checklist:

Home Page:

1. Verify page layout and design
2. Check the navigation menu and links
3. Validate search functionality (if present)
4. Review hero section/content

Inner Pages:

1. About Us
2. Contact/Support
3. FAQ
4. Blog (if present)
5. Terms and Conditions
6. Privacy Policy

Features and Functionality:

1. User registration/login
2. Payment gateway integration (if applicable)
3. Search filters and sorting
4. Product/service details pages
5. Reviews and ratings (if present)
6. Commenting system (if present)

User Experience (UX):

1. Responsive design (mobile, tablet, desktop)
2. Page loading speed
3. Navigation and menu usability
4. Content readability
5. Error handling and messaging

Security:
1. HTTPS encryption
2. Password hashing and storage
3. Input validation and sanitization
4. CSRF protection
5. Secure payment processing

Accessibility:
1. Screen reader compatibility
2. Keyboard navigation
3. High contrast mode
4. Closed captions (if video content)

Browser and Device Compatibility:
1. Test on multiple browsers (Chrome, Firefox, Safari, Edge)
2. Test on different devices (desktop, laptop, mobile, tablet)
3. Verify consistency across devices and browsers

Other:

1. Social media integration
2. Newsletter subscription
3. Contact form functionality
4. Map integration (if present)
5. Third-party services integration (e.g., analytics)

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

How to Run Two Browsers Simultaneously in Selenium WebDriver (With Code Example)

 package TEST;

import org.openqa.selenium.WebDriver;

import org.openqa.selenium.chrome.ChromeDriver;

import org.openqa.selenium.firefox.FirefoxDriver;

public class Selenium_Latest {

public static void main(String[] args) {

// Create and start two threads, one for each browser.

Thread chromeThread = new Thread(new BrowserRunnable("chrome"));

Thread firefoxThread = new Thread(new BrowserRunnable("firefox"));

chromeThread.start();

firefoxThread.start();

}

}

// Runnable class for launching a browser

class BrowserRunnable implements Runnable {

private String browserType;

public BrowserRunnable(String browserType) {

this.browserType = browserType;

}

@Override

public void run() {

WebDriver driver = null;

if (browserType.equals("chrome")) {

driver = new ChromeDriver();

} else if (browserType.equals("firefox")) {

driver = new FirefoxDriver();

}

if (driver != null) {

driver.get("https://suriyaparithy.blogspot.com/");

// Optionally, get the title and print it for each browser

String title = driver.getTitle();

System.out.println(browserType + " Browser - Page Title: " + title);

// Closing the browser after operation

driver.quit();

}

}

}

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Postman Variables Explained: Global vs Environment vs Collection (Key Differences with Examples)

Global Variables:

• Stored globally across all requests and collections.
• It can be accessed from any request or collection.
• Use cases: API keys, common headers, or base URLs

Environment Variables:

• Stored within a specific environment (e.g., dev, staging, prod).
• It can be accessed only from requests within the same environment.
• Use cases: Environment-specific settings, such as URLs, credentials, or timeouts.

Collection Variables:

• Stored within a specific collection.
• It can be accessed only from requests within the same collection.
• Use cases: Collection-specific settings, such as API endpoints, headers, or query parameters.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.