Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Tata Elxsi hiring for Software Testing roles
Tata Elxsi is a Tata Group design and technology services company that works on product engineering for the automotive, media and communications, and healthcare industries. Its teams build embedded software, set-top box and streaming solutions, medical device software and user experience designs. In India it hires software, embedded, testing and design engineers, with a notable development centre in Thiruvananthapuram's Technopark.
For Software Testing roles, this Tata Elxsi practice set focuses most on Manual Testing Basics (7), Bug Life Cycle and Jira (7), Testing Types (6), Database Testing (4). It has 22 easy, 18 medium questions, so you can start easy and work up to the harder ones.
Company type
IT services
Headquarters
Bengaluru, India
Main India offices
Bengaluru, Thiruvananthapuram, Chennai, Pune
Tata Elxsi Software Testing interview process
Online assessment (aptitude + technical)
Technical interview
Managerial round
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for Tata ElxsiStart 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.
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.
02
What is the difference between a test case and a test scenario?
Check that responses return only needed fields, with no passwords, password hashes, full card numbers, full ID numbers or internal keys. Verify personal data is masked where required, for example only the last four digits of a phone number. Look at application and browser console logs for tokens or personal data. Check error responses do not expose stack traces, SQL or server versions. Raise any leak as a high-severity bug.
04
What is a screen reader and which ones are commonly used for testing?
A screen reader is software that reads screen content aloud or sends it to a braille display, used mainly by blind and low-vision people. Common ones are NVDA, a free Windows reader, JAWS, a paid Windows reader common in enterprises, VoiceOver, built into macOS and iOS, and TalkBack, built into Android. Testers usually cover NVDA with a desktop browser plus VoiceOver or TalkBack on mobile.
05
A user updates their phone number in the app, but the old number still appears in reports. What do you check?
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.
06
A developer marks your bug as fixed, but it still fails. What do you do?
First confirm you are testing the right build, which contains the fix, and clear the cache. Repeat the exact steps and data from the bug. If it still fails, reopen the bug with a comment stating the build number, what you did and the actual result, with a fresh screenshot or video. Talk to the developer directly if the steps differ from what they tested, so the fix is not tested on a different scenario.
07
SQL: find orders that have an order date in the future.
-- Orders cannot be placed in the future
SELECT id, order_date, status
FROM orders
WHERE order_date > CURRENT_TIMESTAMP;
-- Expected result: no rows. If rows appear, check time zone handling and input validation.
A latent defect exists in the software but has not caused a failure yet because the needed conditions have not occurred, such as a leap-year bug that appears only on 29 February. A masked defect is hidden by another defect, for example a broken discount calculation you cannot reach because the cart page crashes first. After the first bug is fixed, the masked one appears, which is one reason regression and retesting matter.
The tests verified the specification but did not validate the user experience. The test cases probably checked only functional outcomes and missed usability: unclear labels, too many steps or poor error messages. Next time, add usability heuristics to reviews, do exploratory sessions as a real user persona and involve users in UAT or demos. Log the current feedback as improvement items with clear examples.
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.
14
What are components, labels and fix versions in Jira?
Components are fixed sub-parts of a project, such as Payments or Login, often with a default owner. Labels are free-text tags, such as regression or ui, that anyone can add for grouping. Fix version is the release in which the issue is planned to be fixed, while affects version is where the bug was found. Testers use these fields to filter bugs and to build release-wise reports.
15
What is network condition testing for mobile apps?
It checks app behaviour on different networks: Wi-Fi, 4G, 5G, slow 2G or 3G, high latency, packet loss and no network. Also test switching between Wi-Fi and mobile data in the middle of an action, and airplane mode. The app should show loaders and clear offline messages, retry safely without duplicate actions and not freeze. Network throttling tools in developer options or proxy tools help simulate these conditions.
16
What is the difference between a story, epic, task and bug in JIRA?
A deferred bug is valid, but the team decides to fix it in a later release because of low priority, time limits or low impact. It stays in the backlog with a target version. A rejected bug is one the developer or triage team considers invalid: working as designed, not reproducible, a duplicate or caused by wrong test data. Testers should check the reason for rejection and challenge it with evidence if they disagree.
Open developer tools and use the network tab with cache disabled to see each request's size and time, and the total load time. Look for very large images or scripts, slow API calls and requests that fail or repeat. Use throttling to simulate slow 3G or 4G. Run the built-in performance audit tool to get scores for load speed and suggestions. Record the numbers so you can compare with later builds.
Alt text gives a text alternative for images so screen reader users get the same information. Check that informative images have short, meaningful alt text, such as 'Bar chart showing sales doubled in 2025', that decorative images have empty alt so they are skipped, and that image buttons describe the action, such as 'Search', not the picture. Inspect the alt attribute in developer tools and listen with a screen reader.
21
When is manual testing a better choice than automation?
Manual testing is better for exploratory testing, usability and look-and-feel checks, features that change often, one-time tests and early testing of new functionality. Automation pays off for stable, repetitive tests such as regression suites, data-driven checks and smoke tests run on every build. Most teams combine both: manual for discovery and judgement, automation for speed and repeatability.
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.
24
Design EP and BVA tests for a password that must be 8 to 16 characters and contain at least one digit.
Length partitions: below 8 (invalid), 8 to 16 (valid), above 16 (invalid). Boundaries: 7, 8, 9, 15, 16 and 17 characters. Digit partitions: contains a digit (valid), no digit (invalid). Sample tests: 'abc1234' with 7 characters is rejected, 'abcdefg1' with 8 is accepted, a 16-character value with a digit is accepted, 17 characters is rejected, and 'abcdefgh' with no digit is rejected. Also test empty input and spaces.
Valid login, wrong password, empty fields, case sensitivity, max length, SQL-injection strings, password masking, 'remember me', lock-out after N attempts and the forgot-password link.
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.
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.
28
How do you test biometric login with fingerprint or face unlock?
Test enabling biometrics in app settings after a password login. Verify login with a registered fingerprint or face, and failure with an unregistered one, falling back to PIN or password after the allowed attempts. Remove or add a fingerprint in device settings and check the app asks for re-authentication. Test devices without biometric hardware, disabled biometrics and app behaviour after an OS update or reinstall.
Compliance testing checks that software meets external laws, standards or internal policies, not just functional requirements. Examples include payment security standards for card data, data protection rules for personal data, accessibility guidelines and RBI rules for banking apps. Testers verify items such as consent capture, data retention, audit logs and masking. Findings are usually documented as evidence for auditors, so traceability and clear records matter as much as the tests.
30
What is data masking and why is it used in test databases?
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.
31
How do you convert existing manual test cases into automated scripts?
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.
32
What is the difference between a bug and an enhancement?
Test deliverables are the documents and artefacts produced during testing and shared with stakeholders. Before testing: test plan, test strategy and estimates. During testing: test scenarios, test cases, test data, traceability matrix, execution logs and bug reports. After testing: test summary report, closure report, metrics and lessons learned. The test plan should list which deliverables are expected so nothing is missed at sign-off.
34
What are ACID properties and how can a tester check them?
ACID means Atomicity, Consistency, Isolation and Durability. Atomicity: a transfer that debits one account must also credit the other, or neither happens; test by forcing a failure midway. Consistency: constraints still hold after the transaction. Isolation: two users updating together do not see each other's half-done work; test with two sessions. Durability: committed data survives a restart; test by committing, restarting the service and querying again.
35
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.
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.
Verification: are we building the product right? (reviews, walkthroughs — no code run). Validation: are we building the right product? (actual testing against user needs).
38
Tell me about a time you found a usability problem that the requirements did not mention.
Situation: while testing a leave application form, every test case passed. Task: I still felt the flow was confusing. Action: I noticed the date picker started on Sunday and the half-day option was hidden under 'More', so I asked two colleagues to apply for leave while I watched; both made mistakes. I logged a usability suggestion with notes. Result: product moved the option and support queries dropped.
39
What is the difference between retesting and regression testing?
Retesting, or confirmation testing, checks that a specific bug that was fixed now works, using the same steps as the original bug. Regression testing checks that the fix or a new change has not broken other, previously working features. Retesting is planned for failed cases only, while regression covers a wider set of passing cases. Retesting usually comes first, then regression around the changed area.
40
What is the difference between Scrum and Kanban for a tester?
Scrum works in fixed sprints with planned scope, roles and ceremonies, so the tester plans testing for the sprint and aims to finish all stories by the sprint end. Kanban is a continuous flow with work-in-progress limits and no fixed sprints, so testing happens as each item reaches the test column. In Kanban, a tester watches that the testing column does not become a bottleneck and raises it when limits are hit.
Tips to crack the Tata Elxsi Software Testing interview
Revise C, C++ or Python fundamentals along with operating systems and networking basics for embedded and media engineering roles.
Prepare a crisp walkthrough of your best project, focusing on the problem, your contribution and what you would improve now.
Read about Tata Elxsi's work in automotive software, video streaming and medical devices to show real interest in its domains.
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; Tata Elxsi interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Tata Elxsi Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + technical); Technical interview; Managerial round; 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 Tata Elxsi Software Testing interview?
This practice set leans on Manual Testing Basics (7), Bug Life Cycle and Jira (7), Testing Types (6), Database Testing (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Tata Elxsi interviewers ask you to walk through real work.
Are these the exact questions asked at Tata Elxsi?
No. These are curated practice questions that match the skills and difficulty usually tested in it services interviews like Tata Elxsi's. They are not a leaked or verified list of past questions.
Where does Tata Elxsi hire Software Testing professionals in India?
Tata Elxsi has large teams in Bengaluru, Thiruvananthapuram, Chennai, Pune. Openings and locations change often, so check the Tata Elxsi careers page and filter by city and experience.