Skip to content

Software Testing Interview Questions for Junior Roles (₹4–6 LPA)

40 questions with answers for junior roles — 28 easy, 12 medium.

What ₹4–6 LPA interviews expect

Strong basics with small practical tasks Tools and syntax used day to day Explaining your project work Learning ability and teamwork

About ₹4–6 LPA Software Testing roles

Roles in the ₹4–6 LPA band are typically for junior roles. Interviewers check whether you can already do the work expected at this level, so questions here are weighted towards Automation Basics for Manual Testers (7), Bug Life Cycle and Jira (4), Agile, SQL and API Testing (4), Mobile Testing (4).

Salary bands are indicative only. The same skills can pay differently across cities, company types and negotiation.

Solved in this bandStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
01

Severity vs priority — with an example.

Save to ▾
Show answer
Severity = impact on the system. Priority = urgency to fix. Logo misspelt on the homepage → low severity, high priority. Crash in a rarely used report → high severity, low priority.
02

Write SQL to verify an order was saved correctly.

Save to ▾
Show answer
SELECT status, amount FROM orders WHERE order_id = 'ORD123'; -- compare with the UI, then check the matching rows in order_items
03

What is interrupt testing in mobile apps?

Save to ▾
Show answer
Interrupt testing checks how the app behaves when something interrupts it: an incoming call, SMS, notification, alarm, low battery warning, network change, plugging in a charger or switching to another app. The app should pause correctly, keep the user's data and resume where the user left off. For example, a call during a payment must not cause a double charge or lose the transaction state.
04

What is a duplicate bug and how do you avoid logging one?

Save to ▾
Show answer
A duplicate bug is a new report for a problem that is already logged. Before raising a bug, search the tracker by key words, module, error message and recent open bugs, and ask teammates working on the same area. If a similar bug exists, add your extra information, such as another browser or data set, as a comment instead of a new ticket. This keeps the backlog clean and saves triage time.
05

How do you manage testing for multiple projects with competing deadlines?

Save to ▾
Show answer
Model answer: Situation: I was supporting two products whose releases fell in the same week. Task: deliver both without dropping quality. Action: I listed tasks by release date and risk, agreed priorities with both leads, blocked focus time for each product and shared daily status. I also asked a teammate to take retesting on one project. Result: both releases went out on time with no critical escapes.
06

How do you write test cases when only wireframes are available and the UI is not ready?

Save to ▾
Show answer
Use the wireframes and the user story as the test basis. Write test scenarios and high-level cases for the flows, field validations, navigation and error states shown in the design. Note open questions, such as missing empty states or error messages, and clarify them with the designer. Keep exact UI text and steps light so they are easy to update. Once the build arrives, refine the cases and add any missing details.
07

What is a database view and what do you verify when testing it?

Save to ▾
Show answer
A view is a saved query that behaves like a virtual table, often used for reports or to hide sensitive columns. When testing it, compare its output with the same query run on the base tables, check filters and joins return the right rows, confirm hidden columns such as salary are really absent, check behaviour when base data changes and verify that users without permission on the base tables can still read the view if intended.
08

What is data masking and why is it used in test databases?

Save to ▾
Show answer
Data masking replaces real sensitive values with realistic but fake ones, for example changing real phone numbers to valid-looking dummy numbers and real names to generated names. It lets teams test with production-like data volume and patterns without exposing customer information. It also supports compliance with India's Digital Personal Data Protection Act. Testers should check that masked data still passes validation rules and keeps relationships between tables intact.
09

What are implicit waits, explicit waits and auto-waiting?

Save to ▾
Show answer
An implicit wait, in Selenium, sets a global time the driver keeps retrying to find any element before failing. An explicit wait waits for a specific condition, such as an element being clickable or a spinner disappearing, and is more precise. Auto-waiting, built into Playwright and Cypress, automatically waits for elements to be visible, enabled and stable before acting. Mixing implicit and explicit waits in Selenium can cause unpredictable delays.
10

What is colour contrast ratio and what values does WCAG require?

Save to ▾
Show answer
Contrast ratio compares the brightness of text and its background, from 1:1 to 21:1. WCAG AA requires at least 4.5:1 for normal text and 3:1 for large text, which is about 18 point or 14 point bold. User interface parts such as input borders and icons need 3:1. AAA raises text to 7:1. Testers check this with a contrast checker or browser developer tools, including placeholder, disabled and hover states.
11

Tell me about a disagreement with a developer about a bug's severity.

Save to ▾
Show answer
Model answer: Situation: I logged a bug where the invoice PDF showed the wrong GST number, and the developer marked it minor because the screen value was correct. Task: get the right priority. Action: I explained that customers use the PDF for tax filing and showed the requirement. Result: the product owner agreed it was major, it was fixed before release, and we added PDF checks to regression.
12

How do you test a web page using only the keyboard?

Save to ▾
Show answer
Put the mouse away. Press Tab and Shift+Tab to move through every link, button and field, and check that the order is logical and the focus outline is always visible. Use Enter and Space to activate buttons and links, arrow keys for menus, radio groups and sliders, and Escape to close dialogs. Check that nothing traps focus, hidden items do not receive focus and a skip to main content link works.
13

Which basic Git commands should a manual tester learn before working on automation?

Save to ▾
Show answer
Start with: git clone to copy the test repository; git pull to get the latest changes; git checkout -b feature/login-tests to create a branch; git status and git diff to see changes; git add and git commit -m to save work with a message; and git push to send the branch so you can raise a pull request for review. Also learn to resolve simple merge conflicts and never commit passwords.
14

What does POUR mean in accessibility?

Save to ▾
Show answer
POUR is the four principles behind WCAG. Perceivable: users can see or hear the content, for example images have alt text and videos have captions. Operable: everything works with a keyboard and users have enough time. Understandable: text is clear and forms explain errors. Robust: content works with assistive technologies such as screen readers. Every WCAG success criterion sits under one of these four principles.
15

What are the boundary values for an age field that accepts 18–60?

Save to ▾
Show answer
Test 17, 18, 19, 59, 60 and 61.
16

How is back-end database testing different from front-end UI testing?

Save to ▾
Show answer
UI testing checks what the user sees and does: screens, buttons, messages and flows. Database testing checks what happens underneath: whether the right rows are inserted, updated or deleted, whether constraints hold and whether data stays consistent across tables. A screen can show a success message while the database saved a wrong amount or nothing at all. So testers combine both, using SQL to confirm that every important UI action leaves the database in the expected state.
17

What is a test harness?

Save to ▾
Show answer
A test harness is the setup of drivers, stubs, test data, scripts and tools needed to run tests on a component and collect results, especially when the full system is not available. For example, to test a pricing module, a harness can feed it input files, stub the tax service and compare outputs with expected values. In automation, the framework, runner and reporting together are often called the harness.
18

When should you reopen a bug and when should you log a new one?

Save to ▾
Show answer
Reopen the bug when the same issue, with the same steps and expected result, still fails after the fix. Log a new bug when the fix works but a different problem appears, even in the same screen, or when the original bug has already been closed in a past release. Link the new bug to the old one. Mixing different problems in one reopened ticket confuses tracking and metrics.
19

Tell me about a time you started learning automation while working as a manual tester.

Save to ▾
Show answer
Situation: our regression took three days every release. Task: I wanted to help but knew only manual testing. Action: I spent an hour daily learning Python and Playwright, automated the login and search smoke cases first and asked a developer to review my code each week. Result: in two months my scripts ran in CI on every build, saving about a day per release, and I moved into a hybrid QA role.
20

SQL: find rows where mandatory columns are NULL or empty in a customers table.

Save to ▾
Show answer
-- Mandatory fields: name, email, phone SELECT id, name, email, phone FROM customers WHERE name IS NULL OR TRIM(name) = '' OR email IS NULL OR TRIM(email) = '' OR phone IS NULL OR TRIM(phone) = ''; -- Expected result: no rows
21

What is a test environment?

Save to ▾
Show answer
The hardware, software, data and configuration where testing happens, set up to mirror production as closely as practical.
22

What should a tester verify about HTTPS on a website?

Save to ▾
Show answer
Check every page and API uses HTTPS, and plain HTTP redirects to HTTPS. Verify the certificate is valid, not expired, and matches the domain, with no browser warnings. Look for mixed content, where an HTTPS page loads scripts or images over HTTP. Check login and payment forms submit only over HTTPS and that cookies holding session data have the Secure flag.
23

What is software testing and why is it needed?

Save to ▾
Show answer
Evaluating software to find defects and confirm it meets requirements. It reduces risk, protects users and saves the cost of fixing bugs after release.
24

What are focus order and visible focus, and how do you test them?

Save to ▾
Show answer
Focus order is the sequence in which keyboard focus moves through interactive elements; it should follow the visual reading order. Visible focus means the focused element clearly shows a ring or highlight. Test by pressing Tab through the page and watching where focus goes. Common bugs are focus jumping to the footer, focus going behind an open dialog and designers removing the outline with CSS, leaving keyboard users lost.
25

What is a sprint retrospective?

Save to ▾
Show answer
A team meeting at the end of a sprint to discuss what went well, what did not and what to improve next.
26

What is SQL and why do testers use it?

Save to ▾
Show answer
A language to query databases. Testers use it to verify data saved by the application, prepare test data and check backend results.
27

What is test automation and what problems does it solve?

Save to ▾
Show answer
Test automation means using scripts and tools to run tests, compare results and report them without a person doing each step. It solves slow and repetitive regression, gives fast feedback on every code change in CI, runs the same checks exactly the same way every time and covers many data combinations. It does not replace thinking: exploratory testing, usability judgement and new feature testing still need manual testers.
28

Write a simple Playwright test in TypeScript that logs in and checks the dashboard heading.

Save to ▾
Show answer
import { test, expect } from '@playwright/test'; test('valid user can log in', async ({ page }) => { await page.goto('https://qa.example.com/login'); await page.getByLabel('Email').fill('qa.user@test.com'); await page.getByLabel('Password').fill('Secret@123'); await page.getByRole('button', { name: 'Login' }).click(); await expect(page.getByRole('heading', { name: 'Dashboard' })).toBeVisible(); });
29

What is end-to-end testing?

Save to ▾
Show answer
End-to-end testing checks a complete business flow from the user's first action to the final result, across all connected parts: UI, APIs, database, third-party services and notifications. For example, in online shopping: search a product, add to cart, pay, receive the confirmation email and see the order in the account. It finds integration issues that module-level testing misses, but it is slower and needs stable environments.
30

Which test cases are good candidates for automation?

Save to ▾
Show answer
Good candidates are stable, repeatable and high value: smoke tests, regression of core flows such as login and checkout, data-driven checks with many inputs, API tests and cross-browser runs of the same flow. Poor candidates are features still changing every sprint, one-time tests, tests needing human judgement like look and feel, and flows that are hard to make reliable, such as real OTP or CAPTCHA. Start with what runs most often.
31

You notice full card numbers printed in the application logs. What do you do?

Save to ▾
Show answer
Treat it as a high-severity security defect, because storing full card numbers in logs breaks payment card security rules and creates a data leak risk. Do not copy the card numbers into the bug; use masked examples and the log location instead. Log the bug with restricted visibility and inform your lead and the security contact right away. After the fix, verify new logs are masked and confirm old logs are cleaned.
32

How does testing differ for native, hybrid and mobile web apps?

Save to ▾
Show answer
Native apps are built for one platform and use device features fully, so testing focuses on OS versions, device features, install and update. Hybrid apps wrap web code in a native shell, so you test both the web view rendering and the native bridges like camera access. Mobile web apps run in a browser, so testing is closer to cross-browser and responsive testing. All three need network, screen size and performance checks.
33

Write test cases for a date of birth field.

Save to ▾
Show answer
Verify a valid date is accepted and saved in the right format. Check the minimum age rule, such as 18 years, using boundary dates of exactly 18 today and one day short. Reject future dates and impossible dates like 30 February. Test leap year dates like 29 February 2004. Check manual typing and the picker give the same result, the field is mandatory if required, and the date displays correctly after saving.
34

Why is orientation and screen size testing important?

Save to ▾
Show answer
Mobile users have many screen sizes, resolutions, notches and foldable screens, and they rotate their phones. Rotation can recreate the screen and lose entered data if not handled. Test portrait and landscape on key screens, small and large phones and tablets, and check text does not cut off, buttons stay reachable and the keyboard does not hide input fields. Check entered form data survives rotation.
35

How do you keep yourself updated with testing practices and tools?

Save to ▾
Show answer
Model answer: I follow testing communities and blogs, practise on public demo sites and read release notes of the tools I use. Last month I learned API schema validation from an online course and tried it on a practice API. I also share one new idea in our team chat each week. This keeps me improving and helps the team pick up useful practices without waiting for formal training.
36

What is the V-model?

Save to ▾
Show answer
A development model where each development phase has a matching testing phase, such as requirements with acceptance tests and design with integration tests.
37

How do you capture logs from an Android device for a bug report?

Save to ▾
Show answer
Enable developer options and USB debugging, connect the phone and confirm it is visible with adb devices. Clear old logs with adb logcat -c, reproduce the bug, then save logs with adb logcat -d > crash_log.txt, filtering by the app package or error level if needed. For a crash, search for FATAL EXCEPTION. Attach the log, device model, OS version, app version and a screen recording to the bug.
38

What is Agile testing?

Save to ▾
Show answer
Testing that is continuous and collaborative within each sprint, with testers working alongside developers and product owners from the start.
39

Write a basic Selenium test in Python that opens a page and checks its title.

Save to ▾
Show answer
from selenium import webdriver def test_home_title(): driver = webdriver.Chrome() # Selenium Manager finds the driver try: driver.get('https://qa.example.com') assert 'Home' in driver.title finally: driver.quit()
40

What is a test plan and what does it contain?

Save to ▾
Show answer
A document defining scope, approach, resources, schedule, entry and exit criteria, risks and deliverables of testing.

Frequently asked questions

What do Software Testing interviews for ₹4–6 LPA roles test?

At ₹4–6 LPA the focus is usually on: strong basics with small practical tasks, tools and syntax used day to day, explaining your project work, learning ability and teamwork. This page's set is weighted towards Automation Basics for Manual Testers (7), Bug Life Cycle and Jira (4), Agile, SQL and API Testing (4), Mobile Testing (4).

Which companies pay ₹4–6 LPA for Software Testing roles?

Pay depends on company type, city, skills and negotiation, not only experience. Use the company-wise pages to practise for the specific employers you are targeting, and treat salary bands as a rough guide.

How should I prepare for a ₹4–6 LPA Software Testing interview?

Solve every question here without looking at the answer first, mark the ones you miss, save them to Last-Minute Revision and revise them the night before. Prepare two project stories that show impact at the level expected for ₹4–6 LPA.