01
What is the difference between a test suite and a test run?
Show answer
A suite is a collection of related test cases; a run is one execution of a set of tests against a build.
Tredence Software Testing Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Tredence hiring for Software Testing roles
Tredence is a data science and analytics services company that helps retail, consumer goods, manufacturing, telecom and healthcare clients use data for decisions. It builds data engineering pipelines, machine learning models, supply chain analytics and AI solutions on modern cloud platforms. In India it hires data analysts, data engineers, data scientists and analytics consultants who work closely with global client teams.
For Software Testing roles, this Tredence practice set focuses most on Test Case Design (6), Mobile Testing (6), STLC and Test Planning (4), Manual Testing Basics (4). It has 4 easy, 31 medium, 5 hard questions, so you can start easy and work up to the harder ones.
- Company type
- Analytics
- Headquarters
- San Jose, California, USA
- Main India offices
- Bengaluru, Chennai, Gurugram
Tredence Software Testing interview process
- Online assessment (aptitude + SQL + Python)
- Technical interview (SQL, statistics, ML)
- Case or managerial round
- HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for TredenceStart 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
02
What is error guessing?
Show answer
Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.
03
How do you break a requirement into testable conditions?
Show answer
Read the requirement and identify inputs, outputs, business rules, user roles and states. Turn each rule into a condition with an expected result, then add negative and boundary conditions. For example, 'users can withdraw up to 10,000 per day' becomes: withdraw below the limit, exactly at the limit, above the limit, multiple withdrawals adding up to the limit, and the limit resetting the next day. Each condition then becomes one or more test cases.
04
A user updates their phone number in the app, but the old number still appears in reports. What do you check?
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.
05
How do you do cross-browser testing and choose which browsers to cover?
Show answer
Use analytics to pick browsers and versions that most real users have, plus the ones listed in the requirement, usually the latest two versions of major desktop and mobile browsers. Run the main flows on each and check layout, fonts, forms, date pickers, file upload and JavaScript errors in the console. Use responsive mode for screen sizes, and real devices or a cloud device lab for mobile browsers.
06
What are latent defects and masked defects?
Show answer
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.
07
How do you plan testing for a feature that depends on a third-party service?
Show answer
Identify the integration points and the service's sandbox, limits and test data. Plan to test with a mock or stub early for our logic and error handling, then against the real sandbox for integration. Include failure scenarios: timeout, slow responses, invalid data and the service being down. Add the dependency to the risk list, with contacts and a fallback plan, and confirm production credentials and monitoring before go-live.
08
What is deep link testing?
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.
09
A security reviewer asks you to confirm that passwords and personal data are stored safely. What do you check in the database?
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.
10
What are the characteristics of a good test case?
Show answer
Clear, concise, independent, repeatable, traceable to a requirement, with precise expected results and tested data.
11
How do you test form accessibility, including labels and error messages?
Show answer
Check that every field has a visible label tied to it, so clicking the label focuses the field and a screen reader announces it. Required fields must be indicated in text, not only by colour or an asterisk without explanation. Submit with errors and check that messages are specific, appear next to the field, are announced by the screen reader and focus moves to the first error. Also check autocomplete for name, email and address.
12
A user fills a long form, switches to another app and comes back. What should you test?
Show answer
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.
13
What is the definition of done?
Show answer
A shared checklist for when a story is complete, usually including code review, tests passing, no open critical bugs and documentation updated.
14
Describe a time you missed a bug that reached production.
Show answer
Model answer: Situation: a discount was applied twice when users pressed the pay button quickly. Task: I had tested the feature and missed it. Action: I owned it in the retrospective, helped reproduce and verify the fix, and added double-click and slow network cases to our checklist for all payment buttons. Result: similar issues were caught in later sprints, and I learned to always test repeated actions.
15
A page loads slowly only for some users. How do you investigate as a manual tester?
Show answer
Collect details from affected users: location, device, browser, network and time. Try to reproduce with similar conditions using browser network throttling. Use the browser developer tools network tab to find slow requests, large files or failing calls, and compare with a fast user. Check whether those users have more data, like a long order history. Share the slow request, timing and conditions in the bug for the developers.
16
What are implicit waits, explicit waits and auto-waiting?
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.
17
What are the boundary values for an age field that accepts 18–60?
Show answer
Test 17, 18, 19, 59, 60 and 61.
18
How do you test database integrity using SQL?
Show answer
Verify inserted, updated and deleted rows match UI actions, check constraints, duplicates, NULLs and totals with COUNT and SUM queries.
19
What is API testing and why is it important?
Show answer
Testing services directly without the UI, checking status codes, responses, security and performance. It finds issues early and is faster than UI tests.
20
What is scalability testing?
Show answer
Scalability testing checks how well the system handles growing load by adding resources, such as more servers or bigger machines, and whether performance improves in proportion. For example, if two servers handle 1,000 users, do four servers handle about 2,000 at the same response time? It finds limits that resources cannot fix, such as a single database bottleneck, and helps plan capacity for future growth.
21
How do you test a mobile app when the device storage is almost full?
Show answer
Fill the device storage close to the limit, then install or update the app and confirm a clear message if it cannot proceed. Inside the app, try downloads, photo capture, caching and saving drafts. The app should show a helpful error, not crash or corrupt data. Also check what happens to the local database when a write fails, and whether the app recovers after space is freed.
22
What are test data and how do you prepare them?
Show answer
The inputs used in tests. Prepare using valid, invalid and boundary values from production-like but masked data, spreadsheets or generators.
23
What is normalization and why should a tester understand it?
Show answer
Normalization organises tables to reduce duplicate data, for example storing the customer address once in a customers table instead of repeating it in every order. Testers should understand it because it explains where data lives and which joins are needed to verify a screen. It also shows risk: in a denormalized report table, the same value is copied in many places, so updates must be tested to confirm every copy changes.
24
What is the difference between a test strategy and a test plan?
Show answer
A test strategy is a high-level document, often at organisation or product level, that defines the general approach: test levels, types, tools, environments, automation approach and standards. It changes rarely. A test plan is project or release specific: scope, schedule, resources, entry and exit criteria, risks and deliverables. The plan follows the strategy and applies it to a particular release.
25
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.
26
Write test cases for a file upload feature.
Show answer
Allowed and disallowed formats, size limits, empty file, duplicate names, special-character names, cancel upload, slow network and multiple files.
27
What is a screen reader and which ones are commonly used for testing?
Show answer
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.
28
A bug happens only in production and not in the QA environment. How do you investigate?
Show answer
Collect exact details: user, time, device, browser and request IDs. Compare production with QA for configuration, feature flags, data volume, third-party integrations, versions and caching. Ask for production logs and error traces through the support or dev team. Try to reproduce in QA with production-like data or in a staging environment. Once found, add a test for the gap and fix the environment difference if one caused it.
29
What is state transition testing?
Show answer
Testing how a system moves between states based on events, for example an order going from placed to paid to shipped to delivered.
30
What is interrupt testing in mobile apps?
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.
31
What does quality mean to you as a tester?
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.
32
What sensitive data checks do you do in API responses and logs?
Show answer
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.
33
How do you test biometric login with fingerprint or face unlock?
Show answer
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.
34
Your automated tests pass one by one but fail randomly when run in parallel. How do you fix the test data so tests are independent?
Show answer
Each test should create the data it needs, usually through an API or database helper, use unique values such as an email with a timestamp, and clean up afterwards. Avoid tests that depend on data made by another test or on a shared account other tests change. For fixed reference data, seed it before the suite runs. Independent data allows tests to run in parallel and in any order without random failures.
35
A web app gets slower the longer a user keeps it open. How do you check for a memory leak as a manual tester?
Show answer
A memory leak happens when an application keeps holding memory it no longer needs, so usage grows the longer it runs. A manual tester may notice the app getting slower over a long session, a browser tab using more and more memory in Task Manager or the browser's memory panel, or a mobile app crashing after repeatedly opening and closing a screen. Report the steps, duration and memory readings over time.
36
The developer says "it's not a bug". What do you do?
Show answer
Re-check the requirement, reproduce with clear steps and evidence (screenshots, logs), discuss with the BA/PO and record the final decision.
37
What does the absence-of-errors fallacy mean?
Show answer
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.
38
What are SQL constraints?
Show answer
Rules such as NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY and CHECK that keep data valid and consistent.
39
What is mobile app testing and what extra checks does it need?
Show answer
Test on real devices and OS versions, interrupts such as calls, battery, network changes, gestures, permissions and app store guidelines.
40
What are severity and priority? Give examples.
Show answer
Severity is impact on the system; priority is urgency of the fix. A crash in a rare report is high severity, low priority; a spelling mistake in the logo is low severity, high priority.
Tips to crack the Tredence Software Testing interview
- Practise SQL queries with joins, window functions and aggregations, since SQL is a core part of most Tredence analytics interviews.
- Revise statistics, hypothesis testing and common machine learning models, and be ready to explain them with business examples.
- Prepare for a business case discussion where you structure a retail or supply chain problem and suggest data-driven solutions.
- 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; Tredence interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Tredence Software Testing interview?
Candidates usually go through 4 stages: Online assessment (aptitude + SQL + Python); Technical interview (SQL, statistics, ML); Case or 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 Tredence Software Testing interview?
This practice set leans on Test Case Design (6), Mobile Testing (6), STLC and Test Planning (4), Manual Testing Basics (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Tredence interviewers ask you to walk through real work.
Are these the exact questions asked at Tredence?
No. These are curated practice questions that match the skills and difficulty usually tested in analytics interviews like Tredence's. They are not a leaked or verified list of past questions.
Where does Tredence hire Software Testing professionals in India?
Tredence has large teams in Bengaluru, Chennai, Gurugram. Openings and locations change often, so check the Tredence careers page and filter by city and experience.
Software Testing questions for similar companies
Analytics
EXL
Software Testing interview questions
Noida, Gurugram, Bengaluru +1
View questionsAnalytics
Fractal Analytics
Software Testing interview questions
Mumbai, Bengaluru, Gurugram +1
View questionsAnalytics
Course5 Intelligence
Software Testing interview questions
Mumbai, Bengaluru
View questionsAnalytics
Mu Sigma
Software Testing interview questions
Bengaluru
View questionsAnalytics
Quantiphi
Software Testing interview questions
Mumbai, Bengaluru
View questionsAnalytics
LatentView Analytics
Software Testing interview questions
Chennai, Bengaluru
View questionsMore ways to practise
Company-wise Software Testing questionsPackage-wise Software Testing questionsExperience-wise Software Testing questionsRole-wise Software Testing questionsCity-wise Software Testing questionsMost asked Software Testing questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsSoftware Testing mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsSoftware Testing topic sheets