Software testing interview questions for freshers (with answers)

Software testing is one of the most common starting points for freshers in IT, and its interviews follow a fairly predictable pattern: basic concepts, test design, bug reporting, a little automation, a little SQL and some practical scenarios. If you can answer the questions below in your own words, you will be ahead of many candidates. The answers here are short on purpose, so you can learn the idea and then explain it with your own example.

Why testers matter: some real stories

Interviewers like candidates who understand why testing exists. A 2002 report by the US National Institute of Standards and Technology (NIST) estimated that inadequate software testing infrastructure cost the US economy about 59.5 billion dollars a year, and that better testing could save around 22.2 billion of it. In 2012, the trading firm Knight Capital lost about 440 million dollars in roughly 45 minutes when its trading software started sending unintended orders; later accounts point to a faulty deployment. And in 1999, NASA lost the 125-million-dollar Mars Climate Orbiter after one team's software produced thrust figures in imperial units while another expected metric units. You can use a story like this to answer "Why is testing important?" with something more memorable than a definition.

Part 1: Testing basics

1. What is software testing?

Software testing is the process of checking that software works as expected, finding defects before users do, and giving the team confidence about quality. It includes checking that the right thing was built (validation) and that it was built correctly (verification).

2. What is the difference between QA and QC?

Quality assurance (QA) focuses on the process: standards, reviews and practices that prevent defects. Quality control (QC) focuses on the product: finding defects through testing. A simple way to say it: QA prevents, QC detects.

3. What is the difference between verification and validation?

Verification asks "Are we building the product right?" and is done through reviews and checks against requirements. Validation asks "Are we building the right product?" and is done by running the software to see if it meets user needs.

4. What are the main levels of testing?

Unit testing (small pieces of code, usually by developers), integration testing (how parts work together), system testing (the whole application) and acceptance testing (whether it meets the business need, often by users or clients).

5. What is the difference between manual and automation testing?

In manual testing a person runs the steps and checks the result. In automation testing a script does it. Automation is useful for repetitive checks such as regression tests, while manual testing is better for exploring new features and judging usability.

Part 2: Test design

6. What is a test case and what does it contain?

A test case is a set of steps with expected results used to check one behaviour. It usually has an ID, title, preconditions, steps, test data, expected result and actual result. A good one is clear enough for someone else to run without asking questions.

7. What is the difference between a test scenario and a test case?

A scenario is a high-level idea, such as "Check login". A test case is a detailed set of steps for one situation within it, such as "Login with a valid email and wrong password shows an error".

8. What are boundary value analysis and equivalence partitioning?

Equivalence partitioning groups inputs that should behave the same, so you test one from each group. Boundary value analysis tests the edges of those groups, where mistakes are most common. For an age field that accepts 18 to 60, you would test 17, 18, 60 and 61.

9. What is regression testing?

Regression testing re-checks existing features after a change, to make sure nothing that worked earlier has broken. It is the most common candidate for automation.

10. What is the difference between smoke testing and sanity testing?

Smoke testing is a quick check of the main functions to decide if a build is stable enough for deeper testing. Sanity testing is a narrow check after a small change or fix to confirm that specific area works.

Part 3: Defects and process

11. What should a good bug report include?

A clear title, steps to reproduce, expected result, actual result, environment (browser, device, version), severity, and evidence such as a screenshot or log. The goal is for a developer to reproduce the problem without further questions.

12. What is the difference between severity and priority?

Severity is how serious the defect is for the system. Priority is how soon it should be fixed. A spelling mistake in the company logo may be low severity but high priority; a crash in a rarely used report may be high severity but lower priority.

13. What is the bug life cycle?

A defect is found and logged (new), assigned to a developer, fixed, retested by the tester and then closed if the fix works. If it does not, it is reopened. Other states such as rejected, duplicate or deferred may also appear.

14. What is STLC?

The Software Testing Life Cycle is the set of phases in testing: understanding requirements, planning, designing test cases, setting up the environment, executing tests, and closing with a report.

15. What is Agile testing?

In Agile teams, testing happens continuously throughout short sprints, not only at the end. Testers join planning, clarify requirements, test each story as it is built and work closely with developers.

Part 4: Automation, API and SQL

16. What is Selenium and why is it used?

Selenium is a free, open-source tool for automating web browsers. It was started in 2004 by Jason Huggins at ThoughtWorks to test an internal application, and it grew into one of the most widely used test automation tools. You write scripts in a language such as Java or Python that open a page, click, type and check results.

17. What is the Page Object Model?

It is a design pattern where each web page has its own class that holds its elements and actions. Tests then call those actions. It makes scripts easier to read and maintain, because a change in the page needs to be fixed in only one place.

18. What is API testing and which tools do you know?

API testing checks the requests and responses between systems, without using the screen. You check the status code, response data, headers and error handling. Postman is a common tool for beginners. See our guide to REST APIs to practise the basics.

19. What SQL should a tester know?

Basic SELECT queries with WHERE, ORDER BY, JOIN and GROUP BY, so you can check that data was saved correctly after a test. You do not need advanced database skills, but you should be able to verify records.

20. What is the difference between a test plan and a test strategy?

A test strategy is a high-level approach, usually common to the organisation or product. A test plan is specific to a project and lists scope, schedule, resources, risks and the features to be tested.

Part 5: Scenario and practical questions

Expect questions such as "How would you test a login page?" or "How would you test a pen?". Interviewers want to see structure, not a perfect list. A good pattern is: valid inputs, invalid inputs, boundary values, empty fields, error messages, security basics (for example, whether a password is hidden), performance and usability, and different browsers or devices. Say your assumptions aloud, and ask a clarifying question before you start.

Other common prompts: "You found a bug the developer says is not a bug. What do you do?" (Show evidence, check the requirement, discuss calmly, involve the product owner if needed.) "What do you do when you have limited time?" (Test the highest-risk and most-used features first.) "Tell me about a bug you found." (Use your own project; explain the steps, the impact and what you learned.)

How to prepare in one week

1. Days 1 and 2: revise Parts 1 to 3 and write answers in your own words.
2. Day 3: write 20 test cases for a login page and a registration form on a practice website.
3. Day 4: log three bugs from a practice application with full reports.
4. Day 5: run one Selenium script and one Postman request.
5. Day 6: practise SQL queries on a sample table.
6. Day 7: do a mock interview with a friend and time your answers.

Interviewers can always tell the difference between memorised definitions and real practice. Bring one small testing project and be ready to walk through it. For help choosing between the two broad paths, read manual testing vs automation testing, and for the full path into the field read how to become a QA tester with no experience.

Ready for the next step?

Practise testing on real projects, not only theory. Build real projects in our Testing Automation with AI program. If you would like guidance from people who work in the industry, join our free career guidance workshop or request a free career discovery session. We will look at your background and help you plan what to learn and build next.