Skip to content

Software Testing Interview Questions for Experienced Professionals (₹10–12 LPA)

40 questions with answers for experienced professionals — 1 easy, 35 medium, 4 hard.

What ₹10–12 LPA interviews expect

End-to-end project ownership Performance and quality thinking Stakeholder communication Scenario-based questions

About ₹10–12 LPA Software Testing roles

Roles in the ₹10–12 LPA band are typically for experienced professionals. Interviewers check whether you can already do the work expected at this level, so questions here are weighted towards Agile, SQL and API Testing (9), Test Case Design (6), Mobile Testing (4), Automation Basics for Manual Testers (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

What is mobile app testing and what extra checks does it need?

Save to ▾
Show answer
Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.
02

How do you test API error handling for invalid input?

Save to ▾
Show answer
Send requests with missing required fields, wrong data types, values beyond limits, invalid formats such as a bad email, unknown fields and an empty or malformed JSON body. The API should return a 4xx code such as 400 or 422, a clear error message that names the field, and no stack trace or database details. Also check that nothing was partly saved in the database after the failed request.
03

What is the testing pyramid?

Save to ▾
Show answer
A model with many fast unit tests at the base, fewer API or integration tests in the middle and a small number of UI tests at the top.
04

How do you design test cases for role-based access with admin, editor and viewer roles?

Save to ▾
Show answer
Build a permission matrix with roles as rows and actions as columns, such as create, edit, delete, publish and view, marking allowed or denied from the requirement. Write a positive test for each allowed cell and a negative test for each denied one. Test through the UI and also call the APIs directly, because hidden buttons are not security. Check role changes take effect immediately and that users cannot access other users' data by changing IDs.
05

How do you test database integrity using SQL?

Save to ▾
Show answer
Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.
06

What is the difference between static and dynamic testing?

Save to ▾
Show answer
Static testing reviews documents and code without executing; dynamic testing executes the software to observe behaviour.
07

SQL: find orders whose total does not match the sum of their order items.

Save to ▾
Show answer
SELECT o.order_id, o.total_amount, SUM(i.quantity * i.unit_price) AS items_total FROM orders o JOIN order_items i ON i.order_id = o.order_id GROUP BY o.order_id, o.total_amount HAVING o.total_amount <> SUM(i.quantity * i.unit_price);
08

Managers say the automation test report is hard to understand. What should a useful report include?

Save to ▾
Show answer
A useful report shows total tests run, passed, failed and skipped, the run time, the environment, build number and browser. For each failure it should show the test name, the failing step, the error message, and a screenshot, video or trace, plus logs. Trends across runs help spot flaky tests. Linking failures to Jira bugs or manual case IDs helps managers see real product risk, not just numbers.
09

What is JQL?

Save to ▾
Show answer
JIRA Query Language, used to search issues, for example project = ABC AND status = Open AND priority = High.
10

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

What is a hotfix?

Save to ▾
Show answer
An urgent patch released outside the normal schedule to fix a critical production defect, followed by regression testing and merge back to the main branch.
12

The developer says "it's not a bug". What do you do?

Save to ▾
Show answer
Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.
13

What does INVEST mean for user stories?

Save to ▾
Show answer
INVEST is a checklist for good user stories: Independent, Negotiable, Valuable, Estimable, Small and Testable. For testers, testable is the most important: a story must have clear acceptance criteria so you can say pass or fail. Small stories are easier to test within a sprint. If a story fails INVEST, raise it in refinement rather than discovering the gaps during testing.
14

How do you test a country dropdown that controls a dependent state dropdown?

Save to ▾
Show answer
Check the state list is empty or disabled until a country is selected. Select a country and verify the correct states load. Change the country and confirm the old state selection is cleared and the new list loads. Test countries with no states, a long list with scrolling and search, and default values on page load. Submit the form and verify the saved values, then reload and check both dropdowns keep the saved selection.
15

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

What do you check in mobile accessibility testing?

Save to ▾
Show answer
Turn on the screen reader, TalkBack on Android or VoiceOver on iOS, and check every button, image and field has a meaningful label and the reading order is logical. Check text scales with system font size, colour contrast is sufficient and touch targets are large enough, about 48 by 48 density-independent pixels. Make sure information is not shown by colour alone and that the app works without complex gestures.
17

SQL: find duplicate emails.

Save to ▾
Show answer
SELECT email, COUNT(*) FROM users GROUP BY email HAVING COUNT(*) > 1;
18

What is decision table testing?

Save to ▾
Show answer
List conditions and actions in a table and cover every combination of conditions (rules) — ideal for business rules like loan approval: salary > X AND credit score > Y → approve.
19

How do you decide the priority of test cases?

Save to ▾
Show answer
By business criticality, usage frequency, defect history, risk and dependencies, running high-priority cases first.
20

Write test cases for live order tracking in a food delivery app.

Save to ▾
Show answer
Verify each status change appears in order: placed, accepted, preparing, picked up and delivered. Check the rider's location updates on the map at the expected interval. Test the estimated time updates when there is a delay. Verify notifications for each status. Check behaviour when the network drops and recovers, when the app is reopened, and when the order is cancelled midway. Confirm tracking stops after delivery and the rating screen appears.
21

Tell me about a device-specific bug you found and how you reported it.

Save to ▾
Show answer
Model answer: Situation: users of one budget phone model reported that the camera upload screen was black. Task: reproduce it. Action: I borrowed the same model, found the issue only appeared when the battery saver was on, and logged the bug with the device model, OS version, logs and a video. Result: the developer fixed the camera initialisation, and we added that model to our device matrix.
22

Write test cases for a calculator app.

Save to ▾
Show answer
Basic operations, division by zero, decimals, large numbers, order of operations, clear and backspace, repeated operations and memory keys.
23

A manager says the app has 50,000 daily users, so the load test must run 50,000 virtual users at once. How do you respond?

Save to ▾
Show answer
Explain that daily users are not concurrent users. Of 50,000 users a day, only a fraction are active at the same moment, and even they pause between actions because of think time. Use analytics to find the real peak concurrency and request rate, for example 1,500 concurrent users at peak hour, and model that with a safety margin. Running 50,000 users clicking at once tests a load that never happens and wastes effort.
24

What is localisation and internationalisation testing?

Save to ▾
Show answer
Internationalisation tests that the product can support many languages and formats; localisation tests that a specific locale is correct for text, currency, date and layout.
25

What is a sprint planning meeting and what does QA contribute?

Save to ▾
Show answer
The team selects stories for the sprint. QA helps estimate testing effort, clarifies acceptance criteria and flags dependencies and risks.
26

The UI shows the correct order total, but the database has a different value. What do you check?

Save to ▾
Show answer
Note the order ID and compare the UI value, the API response and the database value to find where they differ. Check if the UI calculates the total on the screen instead of using the saved value, whether taxes, discounts or rounding are applied at different layers and whether a later update job changed the record. Log the bug with all three values, because invoices and reports will use the database figure.
27

How do you test an email notification feature?

Save to ▾
Show answer
Trigger the email from each event, such as signup or order placed, and verify it arrives at the right address within the expected time. Check subject, sender name, personalised fields, amounts and links. Click every link and confirm it opens the right page. Check the layout on desktop and mobile mail apps, the unsubscribe option where required, and that no email is sent for failed or cancelled actions. Use a test mailbox tool in QA.
28

What are SQL constraints?

Save to ▾
Show answer
Rules such as NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY and CHECK that keep data valid and consistent.
29

What is a performance bottleneck and where do bottlenecks usually occur?

Save to ▾
Show answer
A bottleneck is the component that limits the whole system's performance, so adding load beyond it increases response times or errors. Common places are slow database queries or missing indexes, too few database connections or threads, CPU or memory limits on servers, slow third-party APIs, large uncompressed files and chatty code that makes many small calls. Monitoring each layer during a test shows which resource saturates first.
30

What is visual regression testing in automation?

Save to ▾
Show answer
Visual regression testing takes screenshots of pages or components and compares them with approved baseline images to detect unexpected layout, font, colour or spacing changes that functional assertions miss. When a difference crosses a threshold, a person reviews it and either accepts the new baseline or logs a bug. Dynamic content like dates and ads must be masked, and the same browser and screen size must be used to avoid noise.
31

What is deep link testing?

Save to ▾
Show answer
A deep link opens a specific screen inside the app from a URL, email, SMS, QR code or notification. Test that each link opens the correct screen with the right data when the app is installed, closed or running in background. If the app is not installed, it should open the store page or a web fallback. Test links that need login, expired or invalid links, and that parameters cannot be tampered with to access other users' data.
32

You change the order ID in a URL and see another customer's order. What is this and what do you do?

Save to ▾
Show answer
This is an insecure direct object reference, a form of broken access control and a critical security bug, because any user can read other users' data. Stop exploring further beyond what is needed to confirm it, record the request, accounts used and evidence, and log it as a critical bug with restricted visibility. Inform the lead and security contact immediately. The fix is a server-side ownership check on every request.
33

Your test repository has many duplicate and outdated test cases. How do you clean it up?

Save to ▾
Show answer
Export the cases and group them by module and requirement. Mark duplicates, merge them into one well-written case, and retire cases for removed features. Check which cases have not been executed or failed in months and confirm whether they are still valid. Link the remaining cases to requirements so gaps are visible. Do it module by module with peer review, and set a rule that every story update also updates its test cases.
34

A security reviewer asks you to confirm that passwords and personal data are stored safely. What do you check in the database?

Save to ▾
Show answer
Query the users table after signup and confirm the password is not stored in plain text or reversible encoding, but as a salted hash from a slow algorithm such as bcrypt or Argon2. Two users with the same password should have different hashes. Check that card numbers are not stored at all or are tokenised, that personal data like Aadhaar numbers is masked or encrypted, and that logs and audit tables do not copy the raw values.
35

Describe a time an automated test caught a regression that manual testing would have missed.

Save to ▾
Show answer
Situation: a small tax rounding change was made late on a Friday. Task: no manual regression was planned for pricing. Action: our nightly API suite failed one data-driven case where a 3-item cart was off by one rupee; I checked the trace, reproduced it manually and logged it with the failing input. Result: it was fixed before release, and the team agreed to keep pricing tests in the pull request suite.
36

How do you convert existing manual test cases into automated scripts?

Save to ▾
Show answer
Pick a small set of stable, high-value regression cases first. Review each one: make steps precise, remove judgement-based checks and define clear expected results. Prepare test data that the script can create and clean up. Build reusable page objects and helpers for common steps like login. Automate, run several times to confirm stability, then link each script to its manual case ID and mark the manual case as automated.
37

How do you test session management in a web application?

Save to ▾
Show answer
Check that a new session ID is created after login, and that the session expires after the defined idle time. Verify logout invalidates the session on the server, so pressing back or reusing the old cookie does not work. Check that cookies use Secure, HttpOnly and SameSite flags. Test concurrent logins if they are limited, and that changing the password ends other sessions. Session IDs must not appear in URLs.
38

What is shift-left testing and why is it cheaper?

Save to ▾
Show answer
Shift-left means starting testing activities earlier in the life cycle: reviewing requirements, joining design discussions and writing tests before code is complete. A defect found in requirements may cost a short conversation to fix, while the same defect found in production may need a hotfix, data correction and customer support. Testers shift left by asking questions in grooming, defining acceptance criteria and reviewing designs.
39

What goes into a test plan?

Save to ▾
Show answer
Scope (in and out), objectives, approach, environments, schedule, roles, entry/exit criteria, risks and mitigation, deliverables and tools.
40

What is a test basis?

Save to ▾
Show answer
The test basis is the set of documents and knowledge from which test cases are derived. It includes requirement specifications, user stories with acceptance criteria, design documents, wireframes, API contracts, business rules and even existing system behaviour. A good test basis lets you trace each test case back to a requirement. If the test basis is weak or missing, testers must clarify it before or while testing.

Frequently asked questions

What do Software Testing interviews for ₹10–12 LPA roles test?

At ₹10–12 LPA the focus is usually on: end-to-end project ownership, performance and quality thinking, stakeholder communication, scenario-based questions. This page's set is weighted towards Agile, SQL and API Testing (9), Test Case Design (6), Mobile Testing (4), Automation Basics for Manual Testers (4).

Which companies pay ₹10–12 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 ₹10–12 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 ₹10–12 LPA.