Top 30 Manual Testing Interview Questions and Answers for Freshers & Experienced

Top 30 Manual Testing Interview Questions and Answers for Freshers & Experienced

This article covers the most frequently asked manual testing questions with real-time examples, concepts like STLC, bug life cycle, and test techniques. Suitable for both freshers and experienced professionals.

---

1. What is Software Testing?

Software Testing is the process of evaluating a software application to identify defects and ensure it meets the specified requirements.

Real-Time Scenario: Before launching an e-commerce website, testers validate the cart, payment, and checkout functionalities to avoid issues post-launch.

2. What are the different types of Software Testing?

• Manual Testing
• Automation Testing
• Functional Testing
• Non-Functional Testing (Performance, Security, Usability)
• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing

3. What is the Software Testing Life Cycle (STLC)?

STLC is a sequence of activities conducted during testing:

1. Requirement Analysis
2. Test Planning
3. Test Case Development
4. Test Environment Setup
5. Test Execution
6. Test Cycle Closure

Real-Time Example: In a banking app, STLC ensures that login, balance view, and fund transfer are tested in an organised manner.

4. What is the difference between Verification and Validation?

Criteria	Verification	Validation
Definition	Are we building the product right?	Are we building the right product?
Activity Type	Static	Dynamic
Examples	Reviews, Walkthroughs	Testing, UAT

5. Explain the Bug Life Cycle.

States: New → Assigned → Open → Fixed → Retest → Verified → Closed
Alternate States: Rejected, Deferred, Duplicate

Real-Time Scenario: A user reports login failure → Developer fixes it → Tester retests → Marks as Verified → Closed.

6. What is a Test Case?

Test Case ID	TC_001
Functionality	Login
Steps	1. Enter username 2. Enter password 3. Click Login
Expected Result	The dashboard is displayed

7. What is the difference between a Test Case and a Test Scenario?

Feature	Test Case	Test Scenario
Detail Level	Very detailed	High-level idea
Example	Validate login with valid creds	Test login functionality

8. What is a Defect?

A defect is a deviation from the expected result in the application.

Example: The Login button does not redirect to the home page.

9. What is Severity and Priority?

Term	Definition	Example
Severity	Impact of the defect on the system	App crashes → High Severity
Priority	The order in which the defect should be fixed	Fixing login issue → High Priority

10. What is Regression Testing?

Testing existing functionality to ensure new changes haven't broken anything.

Real-Time Scenario: After adding a "Save for Later" feature, re-test the cart, checkout, and payment flows.

11. What is Retesting?

Testing the defect after it’s fixed to verify it's resolved.

12. Difference Between Smoke and Sanity Testing?

Feature	Smoke Testing	Sanity Testing
Purpose	Basic build verification	Verify bug fixes/functional areas
Time	Initial build	After a minor release

13. What is Exploratory Testing?

Testing where test cases are not predefined. Tester explores the app on the fly.

Example: While testing a new travel app, testers explore unusual booking combinations.

14. What is Ad-hoc Testing?

Unplanned testing without documentation.

15. What is UAT (User Acceptance Testing)?

Testing is done by the end-user/client to confirm that the system meets business needs.

16. Difference Between Functional and Non-Functional Testing?

Feature	Functional Testing	Non-Functional Testing
Focus	What system does	How well does the system perform
Example	Login, Signup	Load time, security, UI usability

17. What is a Test Plan?

A document describing test scope, approach, resources, and schedule.

18. Explain Different Test Techniques.

• Equivalence Partitioning
• Boundary Value Analysis
• Decision Table Testing
• State Transition
• Error Guessing

19. What is Boundary Value Analysis?

Test inputs at the edge of input ranges.

Example: For age 18–60, test 17, 18, 60, 61.

20. What is Equivalence Partitioning?

Divides input data into valid and invalid classes.

21. What is a Traceability Matrix?

A document mapping requirements with test cases.

Requirement ID	Test Case ID
REQ-001	TC-001, TC-002

22. How do you handle a situation when a developer disagrees with your defect?

• Provide clear defect steps
• Attach screenshots or logs
• Discuss in defect triage meetings
• Use severity & requirement mapping

23. Explain a real-time scenario where you found a critical bug.

Example: In a food delivery app, placing an order deducted payment, but didn’t place the order. Severity: High, Priority: High.

24. What is Test Data?

Data used during test execution, e.g., usernames, passwords, and product IDs.

25. What are Entry and Exit Criteria?

Entry Criteria: Preconditions before testing start.
Exit Criteria: Conditions to conclude testing.

26. What is Compatibility Testing?

Testing on different browsers, devices, and OS.

27. How do you log bugs in a bug tracking tool (e.g., JIRA)?

1. Select project
2. Click “Create Issue”
3. Fill Summary, Steps to Reproduce, Environment, Severity
4. Attach screenshot/log
5. Assign to the developer

28. What is Risk-Based Testing?

Prioritising testing modules based on business impact and failure probability.

29. What is the difference between QA and QC?

QA (Quality Assurance)	QC (Quality Control)
Process-oriented	Product-oriented
Prevent defects	Identify defects

30. How do you ensure test coverage?

• Use requirement traceability
• Review test cases against each requirement
• Conduct peer reviews
• Track coverage in tools like TestLink or Excel

👋 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.

Top 15 Test Cases for Login Page – Manual & Automation Examples (With Bug Scenarios)

Top 15 Test Cases for Login Page – Manual & Automation Examples (With Bug Scenarios)

Testing a login page is one of the most important tasks in software testing. Whether you’re preparing for a QA interview or writing real-time test cases for your web or mobile application, a login module provides many critical validations. In this post, you’ll learn manual test cases, common bugs, and Selenium automation examples for login functionality.

🔍 Why Login Page Testing Is Important?

• The first point of user interaction with the app
• Security entry point – needs proper validation
• The most common area where users face errors

📝 Top 15 Manual Test Cases for Login Page

Test Case ID	Scenario	Test Steps	Expected Result
TC001	Valid username and password	Enter valid credentials and click Login	The user should be redirected to the dashboard
TC002	Invalid password	Enter a valid username and the wrong password	The error message should appear
TC003	Blank username and password	Leave both fields blank and click Login	Validation messages should be displayed
TC004	Blank username only	Leave the username blank, enter the password, and click Login	The username required message should appear
TC005	Blank password only	Enter username, leave the password blank, click Login	Password required message should appear
TC006	SQL injection attempt	Enter "admin' OR 1=1--" as the username	Input should be rejected and sanitized
TC007	Special characters in the username	Enter special characters like '@#$%'	Error or input validation message should appear
TC008	The password field is masked	Check if the password is displayed as dots or asterisks	Characters should be hidden
TC009	Remember Me checkbox	Select the checkbox and log in	The user should stay logged in on the next visit
TC010	Forgot Password link	Click the link and validate the navigation	The user should go to the reset password screen
TC011	Case sensitivity	Enter uppercase instead of lowercase username	The system should handle case sensitivity properly
TC012	Browser Back button after login	Log in successfully and press the browser back button	The user should not return to the login page or see cached content
TC013	Multiple failed login attempts	Try logging in with the wrong password 5 times	Account lock or CAPTCHA should appear
TC014	Login session timeout	Login and remain idle	The session should expire after the defined timeout
TC015	Mobile responsiveness	Open the login page on mobile devices	The login form should render correctly on smaller screens

🐞 Common Bug Scenarios on Login Page

• Login accepts invalid email or empty credentials
• The password is visible even after clicking the "eye" toggle
• No validation messages for blank fields
• Incorrect redirect after login
• The session has not expired after logging out

🤖 Selenium Automation Example – Valid Login Test

@Test
public void validLoginTest() {
    WebDriver driver = new ChromeDriver();
    driver.get("https://example.com/login");
    
    driver.findElement(By.id("username")).sendKeys("testuser");
    driver.findElement(By.id("password")).sendKeys("testpass");
    driver.findElement(By.id("loginBtn")).click();
    
    String expectedTitle = "Dashboard";
    String actualTitle = driver.getTitle();
    Assert.assertEquals(actualTitle, expectedTitle);

    driver.quit();
}

This Selenium test script verifies a successful login using valid credentials. You can also write negative test cases using invalid passwords and assert error messages.

👋 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.

🔍 Role of AI in Software Testing – What’s Changing?

Artificial Intelligence (AI) is revolutionizing software testing by automating complex tasks, enhancing accuracy, and speeding up delivery cycles. Traditional manual and scripted automation testing often require significant human effort and time. AI brings intelligence, learning capability, and efficiency to testing processes.

🧠 Traditional Testing vs AI-Driven Testing

Feature/Aspect	Traditional Testing	AI-Driven Testing
Test Case Creation	Manual or script-based	Auto-generated using ML from usage patterns
Test Execution	Manual or automated scripts	Intelligent execution, self-healing scripts
Defect Prediction	Based on past human knowledge	Predicts based on data patterns
Test Maintenance	High effort for UI changes	AI auto-updates test cases (self-healing)
Data Handling	Manually prepared test data	AI generates synthetic test data
Test Coverage	Based on human planning	Expanded through AI-driven analysis

🚀 Key Ways AI Is Changing Software Testing

1. Test Case Generation

AI analyzes user behavior, logs, and requirements to automatically generate test cases. This saves time and reduces missed edge cases.

2. Test Suite Optimization

AI identifies redundant or low-value test cases, prioritizing high-risk areas for faster regression cycles.

3. Self-Healing Test Scripts

When UI changes occur (e.g., button ID or label changes), AI automatically updates scripts without manual intervention.

4. Defect Prediction and Root Cause Analysis

Machine Learning models can predict bugs based on historical data and help identify the root cause of test failures.

5. Visual Testing with AI

AI-based visual tools like Applitools use image recognition to detect layout/UI bugs traditional testing might miss.

6. Natural Language Processing (NLP)

Tools like Testim and Mabl use NLP to convert plain English into test cases, simplifying test writing.

7. AI in Performance Testing

AI detects performance bottlenecks, predicts infrastructure needs, and smartly scales during load testing.

🧪 Tools Using AI in Testing

Tool	AI Features Included
Testim	AI-based test case generation and maintenance
Mabl	Intelligent test execution, self-healing tests
Applitools	Visual AI testing and UI validation
Functionize	NLP-based test creation and execution
ACCELQ	Autonomous test generation and planning

✅ Benefits of AI in Testing

• Faster time to market
• Reduced manual effort
• Improved accuracy
• Smarter test coverage
• Adaptive to frequent changes (Agile/CI-CD)

🧩 Challenges & Considerations

• Initial tool learning curve and training data needs
• False positives/negatives from poorly trained models
• Still requires human validation for business logic
• Limited in certain non-functional testing areas (e.g., accessibility)

🔮 The Future Outlook

AI won’t replace testers — it will augment human capabilities. Testers will focus more on strategy, data science, and model validation as routine tasks become automated.

Summary:
“AI in software testing is not just a trend – it’s a shift. Testers are becoming test engineers, using AI to shift from doing to deciding.”

👋 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 Explain Testing Concepts in Tamil

🧪 How to Explain Testing Concepts in Tamil (for Local Learners)

📌 1. Software Testing என்றால் என்ன?

விளக்கம்: ஒரு மென்பொருள் சரியாக வேலை செய்கிறதா, பிழையில்லையா என்பதை பரிசோதிப்பதையே Software Testing என அழைக்கிறோம்.

உதாரணம்: ஒரு மருத்துவமனை செயலியில் நோயாளி டைட்டல் புக் செய்யும் பொழுது, அவன் பெயர், வயது, மருத்துவம் அனைத்தும் சரியாகச் சேமிக்கப்படுகிறதா என்று பார்ப்பது தான் சோதனை.

📌 2. Bug (பிழை) என்றால் என்ன?

விளக்கம்: மென்பொருள் எதிர்பார்த்தபடி வேலை செய்யாமல், தவறான விளைவுகளை தரும் நிலையை “Bug” என்கிறோம்.

உதாரணம்: ஒரு app-ல் "Pay" பட்டனை கிளிக் செய்த பிறகு பணம் விலையில்லை, ஆனால் success message வந்துவிட்டது. இது ஒரு பிழை.

📌 3. Manual Testing (கைமுறை சோதனை):

விளக்கம்: கம்ப்யூட்டரில் உள்ள செயலியை நாமே கையில் ஓட்டி (manually) சோதனை செய்வது.

உதாரணம்: Login செய்யும் பக்கம் திறந்து, சரியான username, password டைப் செய்து, system எப்படி பதிலளிக்கிறது என்று பார்ப்பது.

📌 4. Automation Testing (தானியங்கி சோதனை):

விளக்கம்: ஒரு tool (உதாரணம்: Selenium) பயன்படுத்தி, மென்பொருள் சோதனையை தானாகவே ஓடவைக்கிறோம்.

உதாரணம்: 100 பேர் login செய்யக்கூடியது என்பதை ஒவ்வொன்றாக கையால் சோதிக்காமல், ஒரு program எழுதிவிட்டால் system தான் ஓட்டும்.

📌 5. Test Case (சோதனை வழிமுறை):

விளக்கம்: ஒவ்வொரு செயலை எப்படிச் சோதிக்க வேண்டும் என்ற திட்டமிடல்.

Login பக்கம்:

• Step 1: Username தட்டவும்
• Step 2: Password தட்டவும்
• Step 3: Login பட்டனை அழுத்தவும்

எதிர்பார்ப்பு: முகப்பு பக்கம் வரும்

📌 6. Test Scenario (சோதனை நிலை):

விளக்கம்: பயனர் செயல்முறை அடிப்படையில் பரிசோதிக்க வேண்டிய நிலை.

உதாரணம்: “Patient Appointment Booking” என்பது ஒரு scenario. இதுக்குள் பல test cases இருக்கும் – register, select doctor, select date, confirm.

📌 7. Defect Life Cycle (பிழை வாழ்க்கை சுழற்சி):

விளக்கம்: ஒரு பிழை கண்டுபிடிக்கப்பட்ட முதல் நாளிலிருந்து அது தீர்க்கப்படும் வரை உள்ள நிலைகள்:

• New → Assigned → Open → Fixed → Retest → Closed (அல்லது Reopen)

📌 8. Regression Testing (மீண்டும் சோதனை):

விளக்கம்: புதிய மாற்றங்களால் பழைய அம்சங்கள் பாதிக்கப்படுகிறதா என்பதை சரிபார்ப்பது.

உதாரணம்: “Search Doctor” பக்கத்தில் மாற்றம் செய்தோம். ஆனால் “Book Appointment” வேலை செய்கிறதா என்று மீண்டும் சோதிக்கிறோம்.

📌 9. Performance Testing (திறன் சோதனை):

விளக்கம்: மென்பொருள் வேகமாக வேலை செய்கிறதா, அதிக load-க்கு எதிராக எப்படி செயல்படுகிறது என்று பார்க்கிறோம்.

Tool: JMeter

📌 10. Bug Reporting (பிழை அறிக்கைகள்):

விளக்கம்: கண்டுபிடிக்கப்பட்ட பிழைகளை documentation செய்து development குழுவிடம் தெரிவிப்பது.

Tool: Jira, Bugzilla

✅ Bonus Tip:

உண்மையான ஒப்பீடு: ஒரு பொருள் விற்பனைக்கு வருவதற்கு முன்னால் அதை பரிசோதிக்கும் அளவுக்கு QA முக்கியம். மென்பொருள் என்பது மருந்து போல – சரியாக வேலை செய்யாவிட்டால் ஆபத்து.

👋 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.

A Day in the Life of a QA Working on a Medical App

🩺 A Day in the Life of a QA Working on a Medical App

Working in QA for a medical application isn’t just about writing test cases — it’s about ensuring patient safety, data privacy, and compliance with healthcare regulations. Here's what a typical day looks like for me:

🕘 9:00 AM – Morning Standup

We start the day with a daily stand-up call. The product team, developers, and QAs share updates. For me, this is the time to raise concerns about yesterday’s test results or any blockers in automation runs.

📄 10:00 AM – Reviewing Requirements

Before diving into testing, I read through user stories and FSDs (Functional Spec Documents). In the medical domain, I verify that all HIPAA compliance notes and audit trail requirements are clear.

🧪 11:00 AM – Manual Testing Critical Flows

I start by manually testing critical flows like patient registration, appointment booking, EMR (Electronic Medical Records) viewing, and prescription generation. I focus on edge cases, validation, and field-level security.

💻 1:00 PM – Automation Script Review

Post-lunch, I review the automated Selenium + Java test cases that ran on Jenkins overnight. If any failed, I analyze logs, screenshots, and check whether the failure is due to flaky scripts or actual application issues.

📲 2:30 PM – API Testing with Postman

I test appointment APIs, authentication tokens, and data sync endpoints using Postman. For medical apps, secure transmission of patient data (often in JSON or HL7 format) is critical.

🛡️ 4:00 PM – Compliance & Security Checklist

I perform checks for access control, role-based permissions (Doctor, Nurse, Admin, Patient), and ensure error messages don’t leak sensitive data. I also check that sessions time out securely and that data is encrypted at rest.

📋 5:30 PM – Bug Reporting & Test Case Updates

By end of day, I log all bugs found in Jira, update the test case execution sheet, and document regression impacts if needed. I also prepare for the next day’s test plan and share a status update with the team.

🔚 Final Thoughts

Being a QA in a healthcare app requires technical expertise and a sense of responsibility. One bug can impact real people’s health — so attention to detail and rigorous validation is not optional, it’s mandatory.

If you're working in or planning to join healthcare QA, let me know your experiences or doubts in the comments!

👋 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.