Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Mphasis hiring for Software Testing roles
Mphasis is an Indian IT services company, majority-owned by Blackstone, providing cloud, application, testing, data and cognitive services. It has a strong presence in banking, financial services and insurance clients. In India it hires for software engineers, test engineers, data analysts and data engineers, often for BFSI-focused projects.
For Software Testing roles, this Mphasis practice set focuses most on Manual Testing Basics (7), Bug Life Cycle and Jira (6), Agile, SQL and API Testing (5), STLC and Test Planning (5). It has 20 easy, 19 medium, 1 hard questions, so you can start easy and work up to the harder ones.
Company type
IT services
Headquarters
Bengaluru, India
Main India offices
Bengaluru, Pune, Chennai
Mphasis Software Testing interview process
Online assessment (aptitude + reasoning)
Coding test
Technical interview
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for MphasisStart 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
How is back-end database testing different from front-end UI testing?
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.
Visibility of system status: after clicking Pay, show a progress indicator so users do not click again. Error prevention: disable the Submit button until required fields are valid, or ask for confirmation before deleting an account. Recognition rather than recall: show recently searched items and saved addresses instead of making users remember them. Other heuristics include consistency, user control with undo, and clear help for recovering from errors.
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.
07
What is the difference between a test suite and a test run?
Risk-based testing: cover critical user flows, recent changes and high-defect areas first. Clearly communicate the untested risks and get stakeholder sign-off.
Testing shows presence of defects, exhaustive testing is impossible, test early, defects cluster, the pesticide paradox, testing is context-dependent and absence-of-errors is a fallacy.
11
What is the waterfall model and where does testing fit in it?
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.
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.
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.
PUT replaces the whole resource with the data sent, so fields you leave out may be cleared or reset. PATCH applies a partial update and changes only the fields sent. For example, to change only a user's phone number, PATCH with just the phone field is enough, while PUT expects the complete user object. Testers check that PUT and PATCH behave as documented and that missing fields are handled correctly.
18
What is test automation and what problems does it solve?
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.
Defect removal efficiency shows how many defects the team found before release. DRE = defects found before release divided by (defects found before release plus defects found after release), multiplied by 100. If QA found 90 bugs and users reported 10, DRE is 90 percent. A falling DRE means testing is missing more defects, and the escaped bugs should be analysed to improve test coverage.
It means that finding and fixing many defects does not guarantee success if the system itself does not meet user needs. A bug-free product built on wrong or misunderstood requirements is still a failure. For example, a perfectly working report that shows the wrong business metric is useless to the client. This is why testers validate against real user expectations, not just the written specification.
22
What is the difference between accessibility testing and usability testing?
Accessibility testing checks that people with disabilities can use the product, often against WCAG criteria, using keyboards, screen readers, zoom and contrast tools. Usability testing checks how easily typical users complete tasks, by watching real users and measuring success, time and errors. They overlap, since clear labels help everyone, but a page can pass WCAG and still be confusing, or be easy for most users yet unusable with a screen reader.
Data mapping testing checks that each field on a screen, file or API goes to the correct table and column with the correct format. For example, the Date of Birth field on the signup form must land in users.dob as a date, and the State dropdown must store the state code, not the label. Testers use a mapping document, enter known values in the UI or API and query the database to compare field by field.
The Page Object Model is a design pattern where each page or major component gets a class that holds its locators and actions, such as LoginPage with a login method. Tests call these methods instead of using locators directly. When the login button changes, you update one place instead of fifty tests. Tests become readable, like steps a manual tester would write, and duplication drops. Keep assertions mostly in tests, not page objects.
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.
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.
SDLC is the full software development life cycle; STLC is the testing life cycle: requirement analysis, test planning, test design, environment setup, execution and closure.
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.
401 Unauthorized means the request has no valid authentication, such as a missing, expired or wrong token, so the client should log in again. 403 Forbidden means the user is authenticated but does not have permission for that resource, such as a normal user calling an admin API. Testers verify both: call without a token to expect 401, and call with a low-privilege token to expect 403.
33
SQL: how do you test that a primary key rejects duplicate values?
-- Insert a row, then try the same key again; the second insert must fail
INSERT INTO users (id, email) VALUES (9001, 'a@test.com');
INSERT INTO users (id, email) VALUES (9001, 'b@test.com');
-- Expected: duplicate key or unique constraint error
SELECT COUNT(*) FROM users WHERE id = 9001;
-- Expected: 1
DELETE FROM users WHERE id = 9001;
34
Write a basic Selenium test in Python that opens a page and checks its title.
Rank test cases by business risk and usage: critical flows like login, payment and data saving first, then new features, then high-risk regression from past defects, and cosmetic checks last. Run smoke testing immediately to avoid wasting time on a broken build. Share the reduced plan with the lead and product owner so they know what will not be covered, and get agreement on the remaining risk.
Check that the form data is still there when the user returns after a few seconds and after a longer time. Test when the OS kills the app in background due to low memory, which you can force with developer options, and confirm the app restores state or at least warns the user. Also check session timeout behaviour and that sensitive screens are hidden in the recent apps view if required.
39
What is the difference between a test case and a test scenario?
Common tools are axe DevTools, Lighthouse in Chrome, WAVE and accessibility linters in CI. They quickly catch missing alt text, low contrast, missing labels and invalid ARIA. Their limit is that they find only roughly a third of WCAG issues. They cannot judge whether alt text is meaningful, focus order is logical, error messages make sense or a custom widget works with a screen reader, so manual testing is still required.
Tips to crack the Mphasis Software Testing interview
Learn BFSI basics such as banking transactions, insurance claims and mortgages, since many Mphasis clients are in this domain.
Revise testing concepts, SQL and one programming language well for technical interviews.
Read about Mphasis's Front2Back transformation approach, which the company uses to describe its service model.
Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
Practise the hard questions on this page aloud; Mphasis interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Mphasis Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + reasoning); Coding test; Technical interview; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Mphasis Software Testing interview?
This practice set leans on Manual Testing Basics (7), Bug Life Cycle and Jira (6), Agile, SQL and API Testing (5), STLC and Test Planning (5). Revise those first, then practise explaining one or two of your own projects end to end, because most Mphasis interviewers ask you to walk through real work.
Are these the exact questions asked at Mphasis?
No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like Mphasis's. They are not a leaked or verified list of past questions.
Where does Mphasis hire Software Testing professionals in India?
Mphasis has large teams in Bengaluru, Pune, Chennai. Openings and locations change often, so check the Mphasis careers page and filter by city and experience.