QA and Software Testing Interview Questions for Freshers (with Answers)
Fresher QA interviews check that you understand testing as a discipline before any tool. Expect theory questions, a "write test cases for this" exercise, some SQL, and Selenium or API testing questions if the role mentions automation.
Testing fundamentals
What is the difference between verification and validation?
Verification asks "are we building the product right?" and checks documents, designs and code against the specification through reviews. Validation asks "are we building the right product?" and checks the running software against user needs through testing.
What is the difference between severity and priority?
Severity is how badly the defect affects the system. Priority is how soon it must be fixed. A spelling mistake in the company name on the home page is low severity but high priority; a crash in a rarely used report is high severity but may be lower priority.
Explain the bug life cycle.
New, Assigned, Open (developer works on it), Fixed, Retest, then Closed if it passes or Reopened if it does not. A bug can also be marked Rejected, Duplicate or Deferred.
Smoke, sanity and regression testing: what is the difference?
Smoke testing checks that the main functions of a new build work at all. Sanity testing is a narrow check that a specific fix or change works. Regression testing re-runs existing tests to confirm that a change did not break what worked before.
What are the levels of testing?
Unit testing (single functions, by developers), integration testing (modules working together), system testing (the whole application against requirements) and user acceptance testing (by the client or users).
What is boundary value analysis and equivalence partitioning?
Equivalence partitioning splits inputs into groups that should behave the same and tests one value from each. Boundary value analysis tests the edges of those groups, where bugs cluster: for an age field accepting 18–60, test 17, 18, 60 and 61.
What does a good bug report contain?
A clear title, the environment and build, exact steps to reproduce, expected result, actual result, severity, and evidence such as a screenshot or logs. A developer should be able to reproduce it without asking you anything.
What is the difference between a test scenario and a test case?
A scenario is what to test in one line, such as "verify login". A test case is how: preconditions, steps, test data and the expected result for one specific check.
Automation and API testing
Which locators does Selenium support, and which do you prefer?
ID, name, class name, tag name, link text, partial link text, CSS selector and XPath. Prefer ID when it is stable, then CSS selectors; use XPath when you need to navigate by text or relationship.
Implicit wait versus explicit wait?
An implicit wait tells the driver to wait up to a set time for any element to appear. An explicit wait waits for a specific condition on a specific element, such as being clickable. Explicit waits are more reliable; avoid Thread.sleep.
What is the Page Object Model?
A design pattern where each page of the application has a class holding its locators and actions. Tests call those methods, so when the UI changes you update one class instead of every test.
What do you check when testing an API?
The status code, the response body and its schema, response time, behaviour with invalid input and missing fields, authentication and authorisation, and that the data was actually changed in the database.
What do the common HTTP status codes mean?
200 OK, 201 Created, 400 Bad Request (client sent invalid data), 401 Unauthorized (not logged in), 403 Forbidden (not allowed), 404 Not Found, 500 Internal Server Error.
What is the difference between PUT and PATCH?
PUT replaces the whole resource with what you send. PATCH updates only the fields you send.
How to answer "write test cases for a login page"
Start with the happy path, then go systematically: valid and invalid combinations of username and password, empty fields, boundary lengths, leading and trailing spaces, case sensitivity, special characters and SQL injection strings, password masking, the "forgot password" link, account lockout after repeated failures, session behaviour after logout and the back button, and non-functional checks such as response time, keyboard navigation and layout on mobile. Group them aloud as functional, negative, UI, security and performance: interviewers score the structure more than the count.