Software Testing Interview Questions in Noida

Show answer

Verify a correct OTP within validity logs the user in. Verify a wrong OTP shows an error and an expired OTP is rejected. Check the OTP length and that only digits are allowed. Test resend: it is disabled during the countdown, and the old OTP stops working after resend. Check the maximum number of wrong attempts locks verification. Verify auto-read on mobile, paste support, and behaviour when the network drops during submission.

What are stubs and drivers?

Testing TypesMedium

Show answer

Both are temporary pieces of code used in integration testing when some modules are not ready. A stub replaces a called lower-level module and returns fixed responses, used in top-down testing; for example, a stub payment service that always returns success. A driver replaces a calling higher-level module and sends inputs to the module under test, used in bottom-up testing. In API testing, mock servers play the role of stubs.

What is the difference between a story, epic, task and bug in JIRA?

Show answer

An epic is a large body of work; stories are user-facing slices of it; tasks are technical work items; bugs are defects.

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

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.

What is the difference between a defect and a production incident?

Show answer

A defect is a flaw in the software that makes it behave differently from the requirement, whether found in testing or production. A production incident is an event that disrupts or degrades service for users, such as an outage or a failed payment flow. An incident may be caused by a defect, but also by infrastructure, configuration or third-party failures. Incidents are handled by an incident process first, then linked to defects for the fix.

How do you test battery and memory usage of a mobile app?

Mobile TestingMedium

Show answer

Run typical user sessions on a real device and measure battery drain, CPU and memory with platform profiling tools or the device's battery statistics. Compare with the previous version. Look for background work continuing after the app is closed, GPS left on, frequent network polling and memory that keeps growing, which signals a leak. Test on low-RAM devices too, where the OS kills heavy apps quickly.

What are the levels of testing?

Testing TypesEasy

Show answer

Unit, integration, system and acceptance testing, moving from individual components to the complete product in front of users.

A requirement says the page should load fast. How do you turn it into a test case?

Show answer

The word fast is not testable, so ask the product owner for a measurable target, for example the page loads within 3 seconds on a 4G network for 95 percent of requests. Agree on the conditions: device, network, data size and whether it is first load or cached. Then write the test with those conditions and expected time. Record the agreed number in the story so the expected result is not open to opinion.

What is usability testing?

Testing TypesMedium

Show answer

Evaluating how easy and pleasant a product is to use by observing real users complete tasks and noting confusion.

What is the difference between a bug and an enhancement?

Show answer

A bug is behaviour that deviates from agreed requirements; an enhancement is a new or improved capability beyond the current requirements.

What is the difference between a high-level and a low-level test case?

Test Case DesignEasy

Show answer

A high-level test case states what to test without detailed steps or exact data, for example 'Verify user can reset password using registered email'. A low-level test case gives exact steps, test data and expected results for each step. High-level cases are quick to write and suit experienced testers or changing features. Low-level cases suit regulated projects, new team members and cases that will later be automated.

What are entry and exit criteria?

STLC and Test PlanningMedium

Show answer

Entry criteria are conditions that must be met to start testing (build ready, environment set); exit criteria define when testing can stop (pass rate, no critical defects).

What is localisation and internationalisation testing?

Testing TypesMedium

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.

What is visual regression testing in automation?

Automation Basics for Manual TestersMedium

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.

How do you test an API using Postman?

Show answer

Create a request with method, URL, headers and body, send it, check status and body, add test scripts and save it in a collection.

A user updates their phone number in the app, but the old number still appears in reports. What do you check?

Database TestingMedium

Show answer

First query the main users table to see whether the update was saved. If it was, check where the report reads from: a view, a reporting copy, a cache or a nightly ETL table. The report may simply be stale until the next refresh, which may be by design. If the main table still has the old value, check the API request, the update query and any errors in logs, then log a bug with both query results.

What does quality mean to you as a tester?

Manual Testing BasicsEasy

Show answer

Model answer: To me quality means the product does what users need, reliably, and is easy to use, not just that test cases pass. In my final-year project I tested a library app; all features worked, but students struggled to find the search option. I reported it as a usability issue and the team moved search to the home screen. That taught me to test from the user's point of view as well.

What is defect density?

Show answer

The number of defects per size of software, for example defects per thousand lines of code or per module, used to compare quality.

What are response time, throughput and latency?

Performance and Security BasicsEasy

Show answer

Response time is the total time from sending a request to receiving the complete response, as the user experiences it. Latency is the delay before the first byte of the response arrives, mostly network and waiting time. Throughput is how many requests or transactions the system handles per unit of time, such as 500 requests per second. Good performance usually means low response time at the required throughput.

Write test cases for a coupon code field at checkout.

Show answer

Apply a valid coupon and check the discount and final amount. Test invalid, expired and not-yet-active coupons. Check minimum order value, maximum discount cap and category restrictions. Verify one-time-use coupons cannot be reused and that only one coupon applies if stacking is not allowed. Check case sensitivity and leading or trailing spaces. Remove the coupon and confirm the total resets. Change cart items after applying and verify the discount is recalculated.

Your team wants to copy production data into the QA environment for realistic testing. What do you advise?

STLC and Test PlanningHard

Show answer

Do not copy raw production data into test environments. Use synthetic data generated for the test cases, or masked production data where names, phone numbers, emails, ID numbers and card details are replaced while formats and relationships are kept. Restrict access to test databases and record the data rules in the test plan. This keeps testing realistic and follows India's data protection law and company policy.

How do you test an application when requirements change frequently?

STLC and Test PlanningMedium

Show answer

Keep tests modular, prioritise by risk, use exploratory testing, automate stable parts and keep close contact with product owners.

Why are you interested in a mobile testing role?

Mobile TestingEasy

Show answer

Model answer: Most users in India now use services first on their phones, so mobile quality directly affects customers. In my project I tested a college event app on four phones and found that the registration button was hidden by the keyboard on small screens. Fixing it raised sign-ups. I enjoy the variety of devices, networks and real-life situations that mobile testing involves.

What is a flaky test and what usually causes it?

Automation Basics for Manual TestersMedium

Show answer

A flaky test passes and fails on the same code without any change. Common causes are timing problems such as fixed sleeps or missing waits, tests depending on each other or on shared data, unstable locators, animations, third-party services, test order in parallel runs and environment issues like slow servers. Flaky tests destroy trust in the suite, so teams quarantine them, find the root cause and fix it rather than adding retries forever.

What is CI/CD and how does testing fit?

Automation Basics for Manual TestersHard

Show answer

Code is built and tested automatically on each change; tests are quality gates that stop faulty builds from moving forward.

What is heuristic evaluation and how is it different from a usability test with users?

Accessibility & Usability TestingMedium

Show answer

Heuristic evaluation is an expert review where a few evaluators inspect the interface against known usability principles, such as Nielsen's ten heuristics, and list problems with severity. It is fast and cheap and needs no participants. A usability test watches real users perform tasks and shows where they actually struggle. Heuristic reviews find many obvious issues early, but they can miss problems that only real users with real goals reveal.

Tell me about a time you used a test design technique to reduce the number of test cases.

Test Case DesignEasy

Show answer

Model answer: Situation: in my training project, a registration form had age, state and course fields, and my first draft had over 60 test cases. Task: cut effort without losing coverage. Action: I applied equivalence partitioning and boundary values to age and pairwise combinations for state and course. Result: I covered the same rules with 18 cases, my mentor approved them, and execution finished in half the time.

How do you plan testing for a two-week sprint?

STLC and Test PlanningMedium

Show answer

In sprint planning, review each story's acceptance criteria and estimate test effort, including test data and regression. Write test cases in the first days while development starts. Ask for early builds so testing is spread across the sprint, not crowded at the end. Keep time for regression and bug retesting in the last two or three days. Track progress on the board and raise risks in stand-up.

A manager wants 100 percent test automation. How do you respond?

Show answer

I agree with the goal of faster and more reliable testing, but explain that 100 percent is neither possible nor useful. Exploratory testing, usability, visual judgement and brand-new features need people, and some flows like real payments or OTP are costly to automate reliably. I would propose clear targets instead, such as automating all critical regression and smoke flows, with metrics like regression time cut from three days to four hours.

Your automated accessibility scan shows zero errors. Is the page accessible?

Accessibility & Usability TestingMedium

Show answer

Not necessarily. Automated tools catch only a part of WCAG issues, such as missing labels and contrast. A clean scan still needs manual checks: keyboard-only navigation, focus order, a screen reader pass, meaningful alt text and link names, error handling, zoom and reflow and dynamic content. Report the result as 'no automated violations found' and add the manual checklist outcome before claiming conformance.

What are common HTTP status codes?

Show answer

200 OK, 201 Created, 204 No Content, 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, 500 Internal Server Error.

What do you check in mobile accessibility testing?

Mobile TestingMedium

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.

What is the waterfall model and where does testing fit in it?

Manual Testing BasicsEasy

Show answer

Waterfall is a sequential model: requirements, design, development, testing and deployment happen one after another. Testing starts only after development is complete, so defects in requirements or design are found late and are costly to fix. It suits small projects with stable, well-defined requirements. Its weakness for testers is the late feedback, which is why most teams now use Agile or the V-model.

What is the difference between DELETE and TRUNCATE?