Indian IT services
Envision Enterprise Solutions Test Engineer Interview: Rounds, Questions and Preparation
For Test Engineer roles at companies like Envision Enterprise Solutions
What the job involves
A Test Engineer in Indian IT services manually tests software applications, writes and executes test cases, logs defects, and verifies fixes before release. You work closely with developers and business analysts, often on client projects, and may also do basic automation or API testing. Freshers usually start with manual testing on web or mobile applications and gradually move to tools like Selenium or Postman.
Role and Technical Knowledge
- 1
What is the difference between verification and validation in testing?
Verification checks whether you built the product correctly (reviews, walkthroughs), while validation checks whether you built the correct product (actual execution of tests). Give a simple example like checking a login page requirement versus actually logging in.
- 2
Explain the bug life cycle with the statuses you have used.
Cover New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopened. Mention that a tester logs a defect, the lead assigns it, the developer fixes it, and the tester retests before closing.
- 3
What is the difference between smoke testing and sanity testing?
Smoke testing is a broad, shallow check on a new build to see if it is stable enough for further testing. Sanity testing is a narrow, deep check on a specific fix or feature after a minor change.
- 4
How do you write a good test case? What fields do you include?
Mention test case ID, description, preconditions, test steps, test data, expected result, actual result, and status. Emphasise that steps should be clear enough for another tester to execute without asking you.
Practical Scenarios
- 5
You find a defect, but the developer says it is not a bug. How do you handle it?
Show that you first re-check the requirement and reproduce the issue with clear steps, screenshots, and logs. If needed, involve the test lead or business analyst to confirm expected behaviour, and keep the discussion professional.
- 6
How would you test a login page for an e-commerce website?
Cover valid and invalid credentials, blank fields, password masking, SQL injection basics, forgot password, account lock after multiple failures, and session timeout. Also mention cross-browser and mobile view checks.
- 7
You have to test a new build in two days, but the test cases are not ready. What do you do?
Prioritise based on risk and critical business flows, use exploratory testing, and reuse or update existing test cases. Communicate the plan to your lead and focus first on high-impact areas like payment or login.
- 8
How do you decide when to stop testing?
Mention criteria like test case execution percentage, defect closure rate, no open critical or high-severity bugs, and sign-off from the test lead or client. Also note that deadlines and risk coverage influence the decision.
Tools and Technical Depth
- 9
What SQL queries have you used for testing?
Talk about SELECT with WHERE, ORDER BY, and JOIN to verify data in the database against the UI. Mention checking record counts, duplicate entries, and data integrity after a transaction.
- 10
What is the difference between a test plan, test strategy, and test case?
A test strategy is a high-level document for the organisation or project, a test plan covers scope, schedule, resources, and risks for a specific project, and a test case is a step-by-step check for one condition.
- 11
Have you used any automation or API testing tool? Explain one.
If you know Selenium, mention locating elements, writing a simple script, and running it. For Postman, mention creating a request, checking status codes, and validating response body. Be honest if you have only done a course project.
- 12
What is the difference between severity and priority? Give an example.
Severity is the impact on the application, priority is the urgency to fix. Example: a spelling mistake on the homepage is low severity but high priority, while a crash in a rarely used report is high severity but low priority.
Behavioural and HR Questions
- 13
Why do you want to work as a Test Engineer instead of a developer?
Talk about your eye for detail, interest in quality, and satisfaction from finding issues that save the company money. Avoid saying you could not get a developer job.
- 14
Tell me about a time you found a mistake in your own work or in a team project.
Use a simple college project or internship example. Explain what went wrong, how you identified it, what you did to correct it, and what you learned to prevent it next time.
- 15
Are you comfortable with rotational shifts, relocation, or working on client sites?
Answer honestly but positively. Many IT services projects need shift flexibility or travel, so show willingness while stating any genuine constraints clearly and politely.
- 16
Where do you see yourself in three years in testing?
Show a path from manual testing to automation or specialised testing like API, performance, or security. Mention learning tools, getting certifications, and taking more ownership of test planning.
Coding round
Test Engineer interviews usually include a coding round. Practise planning the solution out loud, then review code the AI writes from your plan, in Python, Java, C++, C or JavaScript.
Ready to try it for real?
Take a timed test or talk through a mock interview for this role, then see your scores.
This is practice material for Test Engineer roles, written with AI. It is not a list of questions Envision Enterprise Solutions or any other company has asked.