Manual Testing Interview Questions for Freshers (2026): 20 Questions With Answers, Test Cases and Bug Reports

If you have been searching for manual testing interview questions for freshers, software testing interview questions and answers, difference between severity and priority, how to write test cases for login page or QA fresher interview preparation, this guide gives you sample answers, worked examples and a one-week plan. It is built for freshers who want a software testing job in Pune and need to explain testing clearly, not just memorise definitions.

Meet Meera. She is a B.Com graduate from Pune who completed a software testing course and wants her first QA job. In her first interview she was asked, “What is the difference between severity and priority?” She knew both words and still gave a muddled answer. We will follow Meera through this guide and fix exactly that kind of moment.

What Testing Interviews Really Check

Testing interviewers rarely want textbook recitation. They want to know three things.

Can you think like a user and like a skeptic?

Can you write clear test cases and bug reports?

Can you explain what you did in your own project?

A candidate who gives a short definition plus a real example almost always beats one who recites a paragraph. That is the pattern every sample answer below follows.

Meera’s story, part 1: Meera had memorised a list of definitions, but when the interviewer asked “give me an example,” she froze. She realised she had learned words, not situations. She decided to attach one real example to every concept before her next interview.

Where Testing Interviews Focus: An Illustrative View

This is an illustrative guide to where preparation pays off. It is not an official pattern, and every company differs.

The 20 Most Asked Manual Testing Interview Questions With Sample Answers

1. What is software testing and why is it needed?
Software testing is checking whether software works as expected and finding defects before users do. It reduces risk, improves quality and saves the cost of fixing bugs after release.

2. What is the difference between verification and validation?
Verification checks whether we are building the product right (reviews, walkthroughs, static checks). Validation checks whether we built the right product (actually running the software against user needs).
Example: reviewing a requirement document is verification; running the login feature to confirm it meets the requirement is validation.

3. What is the Software Testing Life Cycle (STLC)?
STLC is the sequence of testing activities: requirement analysis, test planning, test case design, test environment setup, test execution, and test closure.

4. What is the difference between a test scenario and a test case?
A test scenario is a high-level idea of what to test (“verify login functionality”). A test case is a detailed step-by-step set with inputs, steps and expected results.

5. What is the difference between severity and priority?
Severity is how badly the bug affects the system. Priority is how urgently it should be fixed.
Examples:

• High severity, low priority: the app crashes on a rarely used settings screen.

• Low severity, high priority: a spelling mistake in the company name on the homepage.

• High severity, high priority: payment fails for every user.

6. What is the difference between smoke testing and sanity testing?
Smoke testing is a quick check that the main functions of a new build work, deciding whether deeper testing is worth starting. Sanity testing is a narrow check after a small change or bug fix to confirm that specific area works.

7. What is regression testing?
Regression testing re-runs existing tests after a change to confirm that old features still work and nothing new broke.

8. What is the difference between retesting and regression testing?
Retesting re-runs a failed test case after the bug is fixed to confirm the fix. Regression testing checks that the fix or change did not break other parts of the application.

9. What is black box testing and white box testing?
Black box testing checks behaviour without looking at the code, using inputs and expected outputs. White box testing examines internal code, logic and paths, and is usually done by developers or technical testers.

10. What is the defect (bug) life cycle?
A bug moves through states such as New, Assigned, Open, Fixed, Retest, and then Closed if the fix works, or Reopened if it still fails. Some teams also use Rejected, Duplicate and Deferred.

11. What is boundary value analysis?
It is a design technique that tests values at the edges of an input range, because bugs often occur at boundaries. (Worked example below.)

12. What is equivalence partitioning?
It groups inputs into classes that should behave the same, so you test one value from each class instead of every value. (Worked example below.)

13. What is a test plan?
A test plan is a document describing the scope, approach, resources, schedule, risks and deliverables of testing for a project.

14. What is a Requirement Traceability Matrix (RTM)?
An RTM maps requirements to test cases to make sure every requirement is covered by at least one test.

15. What is exploratory testing?
Exploratory testing is simultaneous learning, test design and execution without fixed scripts, relying on the tester’s experience and curiosity to find unexpected bugs.

16. What is the difference between alpha and beta testing?
Alpha testing is done in-house by internal teams before release. Beta testing is done by a limited group of real users in a real environment before the full launch.

17. What is User Acceptance Testing (UAT)?
UAT is the final check by the client or end users to confirm the software meets business needs before going live.

18. What are the characteristics of a good bug report?
It has a clear title, steps to reproduce, expected and actual results, severity and priority, environment details and evidence such as a screenshot. It is concise, reproducible and neutral in tone.

19. What is the difference between manual and automation testing?
Manual testing is executed by a person following or exploring test cases. Automation uses tools and scripts, such as Selenium, to run tests repeatedly and quickly. Manual testing is better for exploratory and usability checks; automation suits repetitive regression.

20. What do you do if the developer says it is not a bug?
I re-check the requirement and my steps, share clear evidence and reproduction details, and discuss calmly. If we still disagree, I involve the business analyst or team lead to confirm the expected behaviour rather than arguing.

Meera’s story, part 2: Meera rewrote her notes so every question had a definition plus one example. For “severity vs priority” she used the crash-on-settings-screen and the company-name typo examples. In her next mock round she answered in 30 seconds and the interviewer simply nodded and moved on.

Worked Example: Test Cases for a Login Page

Interviewers love this one. Show structure.

Tip: say aloud, “I would cover positive, negative, boundary, usability and security cases.”

Worked Example: Boundary Value Analysis and Equivalence Partitioning

Requirement: An age field accepts values from 18 to 60 inclusive.

Equivalence partitions:

• Invalid (below range): less than 18, for example 10

• Valid: 18 to 60, for example 35

• Invalid (above range): more than 60, for example 70

Boundary values to test:

Say this in the interview: “Instead of testing every age, I’d test one value per partition and then the boundary values, because that is where defects commonly hide.”

Worked Example: A Good Bug Report

Note the reproducibility and the browser comparison. Developers love these details.

SQL Questions in Testing Interviews

Testers use SQL to verify that the data saved matches what the UI showed.

sql

-- Check that a newly registered user was stored
SELECT id, name, email, created_at
FROM users
WHERE email = 'meera@example.com';

-- Find duplicate emails (a classic data-quality bug)
SELECT email, COUNT(*) AS cnt
FROM users
GROUP BY email
HAVING COUNT(*) > 1;

-- Count orders per status to cross-check a report
SELECT status, COUNT(*) FROM orders GROUP BY

-- Check that a newly registered user was stored
SELECT id, name, email, created_at
FROM users
WHERE email = 'meera@example.com';

-- Find duplicate emails (a classic data-quality bug)
SELECT email, COUNT(*) AS cnt
FROM users
GROUP BY email
HAVING COUNT(*) > 1;

-- Count orders per status to cross-check a report
SELECT status, COUNT(*) FROM orders GROUP BY

-- Check that a newly registered user was stored
SELECT id, name, email, created_at
FROM users
WHERE email = 'meera@example.com';

-- Find duplicate emails (a classic data-quality bug)
SELECT email, COUNT(*) AS cnt
FROM users
GROUP BY email
HAVING COUNT(*) > 1;

-- Count orders per status to cross-check a report
SELECT status, COUNT(*) FROM orders GROUP BY

Automation Basics: A Simple Selenium Test in Java

Even for manual-testing roles, interviewers may ask whether you understand automation. A tiny example:

java

WebDriver driver = new ChromeDriver();
driver.get("https://example.com/login");

driver.findElement(By.id("username")).sendKeys("testuser");
driver.findElement(By.id("password")).sendKeys("Test@123");
driver.findElement(By.id("loginBtn")).click();

String title = driver.getTitle();
Assert.assertEquals(title, "Dashboard");   // expected vs actual

driver.quit();

WebDriver driver = new ChromeDriver();
driver.get("https://example.com/login");

driver.findElement(By.id("username")).sendKeys("testuser");
driver.findElement(By.id("password")).sendKeys("Test@123");
driver.findElement(By.id("loginBtn")).click();

String title = driver.getTitle();
Assert.assertEquals(title, "Dashboard");   // expected vs actual

driver.quit();

WebDriver driver = new ChromeDriver();
driver.get("https://example.com/login");

driver.findElement(By.id("username")).sendKeys("testuser");
driver.findElement(By.id("password")).sendKeys("Test@123");
driver.findElement(By.id("loginBtn")).click();

String title = driver.getTitle();
Assert.assertEquals(title, "Dashboard");   // expected vs actual

driver.quit();

What to say: “Selenium automates a browser. I locate elements using locators such as id, name, XPath or CSS selector, perform actions, then assert the expected result.”

“Quality is not an act, it is a habit.” — Will Durant (often attributed to Aristotle)

The Classic Practical Question: “How Would You Test a Pen?”

This tests thinking structure, not pen knowledge. Use a framework.

Say it in this order and the interviewer sees a tester’s mind.

Myths vs Reality in Testing Careers and Interviews

Diagnostic: If You Fail Testing Interviews, Check This

Your 7-Day Testing Interview Plan

• Day 1: Concepts. STLC, verification vs validation, black box vs white box. Add an example to each.

• Day 2: Testing types. Smoke, sanity, regression, retesting, exploratory, UAT.

• Day 3: Test design. Write test cases, boundary value and equivalence partitioning examples.

• Day 4: Bug reporting. Write five bug reports using the template; practise severity vs priority.

• Day 5: SQL basics. Select, where, joins, group by, having on a practice database.

• Day 6: Automation intro. Understand locators and run one Selenium test.

• Day 7: Mock interview. Practise the 20 questions aloud and your project story, then review weak answers.

Meera’s story, part 3: After a week of this plan Meera walked into her next interview with a login test-case table in her head, a bug-report template she could recite and a project story with one real defect she had found. She was asked to test a vending machine, used the pen framework, and was offered the role after the HR round. She read the offer letter carefully before signing.

How VibrantMinds Helps Freshers Build a Testing Career

VibrantMinds Technologies Pvt. Ltd. offers a Software Testing programme in Pune designed for freshers, including those from non-IT backgrounds.

• Manual and automation training: The Software Testing (Manual + Automation) course covers test case design, the software testing life cycle, bug tracking, SQL and Selenium basics, the same topics asked in the interview questions above.

• Practice with real artifacts: writing test cases, bug reports and SQL checks gives you the “examples” interviewers want.

• Interview and HR preparation: the placement pipeline includes interview support, and VibrantMinds courses include communication and interview preparation.

• Drive coordination: check the campus-drives portal at https://candidates.vibrantminds.in/ for current openings, and join the WhatsApp groups below for alerts.

• Honesty first: VibrantMinds offers placement support, not a guaranteed job, and no legitimate recruiter should ask you to pay to be interviewed.

VibrantMinds works as a talent ecosystem connecting candidates, colleges and companies, with 1900+ partner colleges and 600+ hiring companies. Learn more on the official website: https://vibrantminds.in/

VibrantMinds Courses at a Glance

Fees, syllabus and batch dates are on https://candidates.vibrantminds.in/. Please confirm them directly before enrolling.

The VibrantMinds Placement Pipeline: Six Steps

Real Outcomes: What to Expect and What Not To

Past students have shared positive feedback about the training and support, and have gone on to roles at companies such as Aress Software and Education Technologies, Saama Technologies and Three M Software. Results vary by candidate, skill level, effort and market conditions, so please confirm details directly with the VibrantMinds team. No one can honestly promise a guaranteed job.

Join the VibrantMinds WhatsApp Groups for Fresher Job and Drive Alerts

Fresher openings, campus drives and walk-in interviews are shared here as they come in. Join whichever group has space; all three carry the same type of updates.

• VibrantMinds Fresher IT Jobs, Group 1: https://chat.whatsapp.com/CUCS1derlmTFee2c9dyUHd

• VibrantMinds Fresher IT Jobs, Group 2: https://chat.whatsapp.com/FvMf1fGYQYnHppQ8AwFX40

• VibrantMinds Fresher IT Jobs, Group 3: https://chat.whatsapp.com/I7RNnGMkb2L8S8HibdyWpQ

Never pay to apply. Legitimate recruiters do not charge candidates for tests, interviews or offer letters. Do not share sensitive personal or financial details in any group chat.

Visit or Contact VibrantMinds in Pune

• Company: VibrantMinds Technologies Pvt. Ltd.

• Address: Viva Academy Building, Warje, Pune, Maharashtra 411052

• Phone: +91 95035 79517

• Email: support@vibrantmindstech.com

• Website: https://vibrantminds.in/

• Candidate portal and courses: https://candidates.vibrantminds.in/

Frequently Asked Questions

What are the most common manual testing interview questions for freshers?
The most common are the difference between verification and validation, severity vs priority, smoke vs sanity testing, regression vs retesting, the bug life cycle, test case vs test scenario, boundary value analysis and how to write a good bug report.

What is the difference between severity and priority in testing?
Severity is how seriously a bug affects the system, while priority is how soon it should be fixed. A crash on a rarely used screen is high severity but low priority, whereas a typo in the company name on the homepage is low severity but high priority.

How do I write test cases for a login page?
Cover valid login, invalid password, empty fields, case sensitivity, account lockout, password masking, forgot-password link and basic security checks, each with steps, test data and expected results.

Do I need to learn automation for a manual testing job?
Not always, but basic knowledge of Selenium and locators improves your chances, and many manual testers later move into automation.

Is SQL required for testing jobs?
Often yes. Testers use SQL to verify that data saved in the database matches what the application shows.

Can a non-IT graduate become a software tester?
Yes. Many testers come from non-IT backgrounds after structured training, practice with test cases and bug reports, and project work.

What is the salary of a fresher software tester in Pune?
It varies by company, role and your interview performance, so treat any published figure as indicative and rely on the actual offer letter.

How should I answer “How would you test a pen?”
Use a framework: functional, usability, performance, reliability, safety, compatibility and negative testing. It shows structured thinking rather than guesswork.

How long does it take to prepare for a testing interview?
If your basics are reasonable, one to two weeks of focused practice on concepts, test cases, bug reports and SQL can help, but your starting level matters more than any fixed timeline.

Does VibrantMinds offer software testing training in Pune?
Yes. VibrantMinds offers a Software Testing (Manual + Automation) programme in Pune covering test case design, STLC, bug tracking, SQL and Selenium basics, with placement support. It does not guarantee a job, so please confirm current details directly with the team.

Final Thoughts: Meera’s Ending, and Yours

A good tester does not just find bugs. A good tester explains them clearly.

If you are in Pune and want guided software testing training with placement support, visit https://vibrantminds.in/, check the candidate portal at https://candidates.vibrantminds.in/, and join the WhatsApp groups above for the next drive.