Skip to content
Software Testing
All courses OffersPlacement Report
‹ Back to previous sectionCourse homeAll page URLs

Software Testing Interview Questions in Indore

36 practice questions with answers for Software Testing interviews in Indore.

Software Testing jobs in Indore

Indore is one of central India's fastest-growing IT hubs, with IT-services campuses and product start-ups in its Super Corridor and IT parks. Companies here hire many freshers and value hands-on project work.

Below are 36 questions that match the mix of service, product and domain employers hiring software testers in Indore.

Solved for IndoreStart 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 do you write a good accessibility bug report?

Accessibility & Usability TestingMedium
Save to ▾
Show answer
Give a clear title, such as 'Checkout: Place Order button not reachable by keyboard'. Include the page URL, browser, operating system and assistive technology with versions. Write exact steps, what was announced or happened, and what was expected. Add the WCAG success criterion, such as 2.1.1 Keyboard, and the user impact. Attach a screenshot or audio recording, and suggest a fix when obvious. Severity should reflect whether users are fully blocked.
02

What are implicit waits, explicit waits and auto-waiting?

Automation Basics for Manual TestersMedium
Save to ▾
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.
03

What is a sprint retrospective?

Agile, SQL and API TestingMedium
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.
04

How can you do basic performance checks with browser developer tools?

Performance and Security BasicsEasy
Save to ▾
Show answer
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.
05

What is error guessing?

Test Case DesignMedium
Save to ▾
Show answer
Using experience to guess where defects likely hide, such as empty fields, special characters or unexpected sequences, and designing tests for them.
06

A security scan says your login page can be loaded inside a frame on other sites. What is the risk and how do you confirm it?

Performance and Security BasicsHard
Save to ▾
Show answer
Clickjacking tricks a user into clicking something on your site while it is hidden inside a frame on an attacker's page, for example a hidden Transfer button under a fake Play button. A tester checks whether sensitive pages can be loaded in an iframe on another site, and inspects response headers for Content-Security-Policy frame-ancestors or X-Frame-Options set to DENY or SAMEORIGIN. If the page loads in the frame, log it.
07

What is performance testing and its types?

Performance and Security BasicsMedium
Save to ▾
Show answer
Measuring speed and stability: load (expected users), stress (beyond limits), spike (sudden surge), endurance (long duration) and scalability testing.
08

Tell me about a time you found a usability problem that the requirements did not mention.

Accessibility & Usability TestingMedium
Save to ▾
Show answer
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.
09

How do you calculate test execution progress and pass rate?

STLC and Test PlanningEasy
Save to ▾
Show answer
Execution progress = test cases executed divided by total planned test cases, multiplied by 100. Pass rate = test cases passed divided by test cases executed, multiplied by 100. For example, if 200 cases are planned, 150 are executed and 120 passed, progress is 75 percent and pass rate is 80 percent. Report blocked cases separately because they are neither passed nor failed.
10

Write a JQL query for open high or highest priority bugs in the current sprint of project PAY.

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
project = PAY AND issuetype = Bug AND statusCategory != Done AND priority in (Highest, High) AND sprint in openSprints() ORDER BY priority DESC, created ASC
11

How do you do cross-browser testing and choose which browsers to cover?

Testing TypesMedium
Save to ▾
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.
12

What are the characteristics of a good test case?

Test Case DesignMedium
Save to ▾
Show answer
Clear, concise, independent, repeatable, traceable to a requirement, with precise expected results and tested data.
13

An API returns 200 OK but the body contains an error message. Is that a bug?

Agile, SQL and API TestingMedium
Save to ▾
Show answer
Usually yes. Status codes should reflect the result so clients and monitoring can react correctly; an error with 200 can hide failures and break retries. A validation error should return 400 or 422, a missing resource 404 and a server failure 500. Check the API contract first: some legacy APIs document this pattern. If it is not documented, log it as a defect with the request and response attached.
14

SQL: find duplicate emails.

Agile, SQL and API TestingMedium
Save to ▾
Show answer
SELECT email, COUNT(*) FROM users GROUP BY email HAVING COUNT(*) > 1;
15

What do you check in mobile accessibility testing?

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

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

Manual Testing BasicsMedium
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.
17

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

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

What is a bug triage meeting?

Bug Life Cycle and JiraMedium
Save to ▾
Show answer
A regular review where QA, development and product assess new bugs and decide severity, priority, owner and target release.
19

What is the difference between a test suite and a test run?

STLC and Test PlanningMedium
Save to ▾
Show answer
A suite is a collection of related test cases; a run is one execution of a set of tests against a build.
20

Write a CSS selector and an XPath for a Login button that has the attribute data-testid='login-btn' and the text Login.

Automation Basics for Manual TestersMedium
Save to ▾
Show answer
/* CSS selector using the test id */ button[data-testid='login-btn'] // XPath using the test id //button[@data-testid='login-btn'] // XPath using the visible text //button[normalize-space()='Login']
21

SQL: how do you test that a primary key rejects duplicate values?

Database TestingEasy
Save to ▾
Show answer
-- 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;
22

How do you test session management in a web application?

Performance and Security BasicsMedium
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.
23

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

Performance and Security BasicsHard
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.
24

What is a test readiness review?

STLC and Test PlanningMedium
Save to ▾
Show answer
A test readiness review is a checkpoint before formal test execution starts, where the team confirms everything needed is in place. It checks that the build is deployed and smoke tested, the environment and test data are ready, test cases are reviewed and approved, access and tools work, and entry criteria are met. It prevents wasted days when execution starts and testers discover a missing service or empty database.
25

How do you break a requirement into testable conditions?

Manual Testing BasicsMedium
Save to ▾
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.
26

Tell me about a time you had to learn SQL or API testing quickly for a project.

Agile, SQL and API TestingEasy
Save to ▾
Show answer
Model answer: Situation: in my first project, testers had to verify orders in the database, and I knew only basic SELECT. Task: become useful within a week. Action: I practised joins on a copy of the test database every evening and asked a senior to review my queries. Result: by the second sprint I was validating order data on my own and caught a missing tax column bug.
27

A CAPTCHA on the signup page blocks screen reader users. What do you recommend?

Accessibility & Usability TestingMedium
Save to ▾
Show answer
Log it as a high-severity accessibility bug because it fully blocks a group of users from signing up. An image-only CAPTCHA fails WCAG unless an alternative is offered. Recommend options such as invisible or risk-based bot checks, an email or OTP verification step, an audio alternative plus another modality, and rate limiting on the server. Retest the full signup with NVDA and TalkBack after the change.
28

What is the difference between a test case and a test scenario?

Manual Testing BasicsEasy
Save to ▾
Show answer
A scenario is a high-level thing to test (user logs in); test cases are the detailed steps and data that verify it.
29

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

Automation Basics for Manual TestersMedium
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.
30

How do you verify database schema changes in a new release?

Database TestingHard
Save to ▾
Show answer
Get the migration script or change list. Compare the schema before and after: new tables and columns, data types, lengths, default values, NULL rules, indexes and constraints. Check that existing data was migrated correctly, for example a new status column filled for old rows. Run the main app flows to confirm queries still work. Finally, confirm the rollback script works on a copy, so the release can be reversed safely.
31

Tell me about a time you designed tests for a feature with unclear requirements.

Test Case DesignMedium
Save to ▾
Show answer
Model answer: Situation: I got a story for 'flexible EMI options' with only one line of description. Task: test it within the sprint. Action: I listed my assumptions on tenure, interest and rounding, reviewed them with the product owner in a 15-minute call, and wrote test cases only after we agreed. Result: three rules were changed before coding finished, and the feature passed UAT without rework.
32

What is a test case and its components?

Manual Testing BasicsEasy
Save to ▾
Show answer
A set of steps with inputs and expected results. Components: ID, title, preconditions, steps, test data, expected result, actual result and status.
33

What does POUR mean in accessibility?

Accessibility & Usability TestingEasy
Save to ▾
Show answer
POUR is the four principles behind WCAG. Perceivable: users can see or hear the content, for example images have alt text and videos have captions. Operable: everything works with a keyboard and users have enough time. Understandable: text is clear and forms explain errors. Robust: content works with assistive technologies such as screen readers. Every WCAG success criterion sits under one of these four principles.
34

What is a user story and what are acceptance criteria?

Agile, SQL and API TestingEasy
Save to ▾
Show answer
A user story describes a feature from the user's view, usually as: As a role, I want a goal, so that a benefit. Acceptance criteria are the specific conditions the story must meet to be accepted, often written as Given, When, Then. For example, given a registered user, when they enter a wrong password three times, then the account is locked for 15 minutes. Testers use acceptance criteria as the base for test cases.
35

How do you set up and clean test data for database tests without affecting other testers?

Database TestingMedium
Save to ▾
Show answer
Create your own data with a clear prefix or tag, such as emails starting with qa_ravi_, or IDs in a reserved range. Insert data through the app or API where possible so it follows real rules, and keep SQL setup scripts in version control. After testing, delete only your tagged rows, or run inside a transaction and roll back. Never edit shared master data without telling the team.
36

What is accessibility testing?

Testing TypesMedium
Save to ▾
Show answer
Checking that people with disabilities can use the product, using screen readers, keyboard navigation, colour contrast and WCAG guidelines.

Companies with offices in Indore (1)

IT services

YASH Technologies

Software Testing interview questions

  • 40 questions
  • 4 rounds

Indore, Pune, Hyderabad

View questions

Few big employers listed in Indore?

Many Indore candidates also apply to teams in Pune and to remote or hybrid roles. Practise the Pune set as well.

Software Testing questions in Pune

Frequently asked questions

Which companies hire Software Testing professionals in Indore?

Companies with large offices in Indore include YASH Technologies. Use their company pages below to practise employer-specific sets.

Are Software Testing interviews in Indore different from other cities?

The questions depend more on the company than the city. Indore's mix of employers decides the style: Companies here hire many freshers and value hands-on project work

How do I find Software Testing jobs in Indore?

Shortlist companies with Indore offices, keep your CV focused on Software Testing projects, apply on company career pages and job portals with the Indore filter, and practise the questions on this page before each interview.

Other cities

DelhiNoidaGurgaonBangaloreHyderabadPuneChennaiMumbaiKolkataAhmedabadJaipurLucknowChandigarhKochiCoimbatoreBhubaneswarNagpurVisakhapatnamThiruvananthapuram

More 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