Infostretch India Test Engineer Interview: Rounds, Questions and Preparation

What the job involves

Test Engineers in Indian IT services validate software applications by writing and executing test cases, reporting defects, and ensuring quality before release. They work closely with developers and business analysts in Agile teams, often on client projects across domains like banking, healthcare, or e-commerce. Day to day involves manual testing, basic automation, and participating in defect triage calls.

Role and Technical Knowledge

1. 1

   What is the difference between verification and validation in software testing?

   Explain verification as 'are we building the product right?' (reviews, static testing) and validation as 'are we building the right product?' (dynamic testing, execution). Give a simple example like a requirements review versus running test cases.

2. 2

   Explain the defect life cycle with a real example.

   Cover stages: New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopen. Use a scenario like a login button not working, and mention how a tester logs it in JIRA and tracks it until closure.

3. 3

   What are boundary value analysis and equivalence partitioning? Give an example.

   Define both techniques and apply them to an input field (e.g., age 18-60). For boundary value, test 17, 18, 19, 59, 60, 61. For equivalence partitioning, divide into invalid (below 18), valid (18-60), and invalid (above 60).

4. 4

   How do you write a good test case? What are the key elements?

   Mention test case ID, description, preconditions, steps, expected result, actual result, and status. Emphasise clarity, reusability, and traceability to requirements.

Practical Scenarios and Tools

1. 5

   You have a login page with username and password. How would you test it?

   Cover positive (valid credentials), negative (invalid username, invalid password, both wrong), boundary (empty fields, max length), security (SQL injection, password masking), and usability (tab order, enter key). Mention test data preparation.

2. 6

   What is the difference between a test plan, test strategy, and test case?

   Test plan is a document outlining scope, approach, resources, and schedule for a project. Test strategy is a high-level document defining testing approach across projects. Test case is a detailed step-by-step procedure for a specific scenario.

3. 7

   How would you test an API using Postman?

   Describe creating a request, setting method (GET, POST), adding headers and body, sending it, and validating status code, response time, and response body. Mention using collections and environment variables for different environments.

4. 8

   What is the difference between severity and priority? Give an example.

   Severity is impact on functionality, priority is urgency to fix. Example: a company logo missing on the homepage has low severity but high priority; a crash on a rarely used feature has high severity but low priority.

Behavioural and Situational Questions

1. 9

   Tell me about a time you found a bug that others missed. How did you handle it?

   Use STAR format: Situation (project), Task (your testing responsibility), Action (how you explored edge cases), Result (bug fixed, impact avoided). Highlight attention to detail and communication with developers.

2. 10

   How do you handle a situation where a developer says your bug is not reproducible?

   Show patience and collaboration. Explain that you would provide detailed steps, screenshots, logs, and environment details. Offer to reproduce together and check if it is environment-specific or intermittent.

3. 11

   Describe a time you had to meet a tight deadline. How did you prioritise testing?

   Mention risk-based testing: focus on critical functionalities first, use smoke and sanity tests, and communicate clearly about what can and cannot be covered. Show ability to stay calm and organised.

4. 12

   Why do you want to work as a Test Engineer in an IT services company?

   Connect interest in quality assurance, problem-solving, and learning automation. Mention exposure to diverse domains and client projects. Avoid saying it is a backup option; show genuine enthusiasm for testing.

HR and Company Fit

1. 13

   Are you willing to relocate or work in shifts based on project requirements?

   Be honest and flexible. If you are open, state it clearly and mention adaptability. If not, explain your constraints politely and show willingness to adjust where possible.

2. 14

   What are your salary expectations for this fresher role?

   Research typical fresher salaries in Indian IT services (e.g., 3-4.5 LPA for smaller companies). Say you are open to the company's standard fresher package and focus on learning and growth.

3. 15

   Where do you see yourself in three years?

   Show a path from manual testing to automation or test lead. Mention gaining certifications (ISTQB) and deepening domain knowledge. Align your growth with the company's needs.

4. 16

   Do you have any questions for us?

   Ask about training programs, project allocation, mentorship, or the tech stack used. Avoid asking about salary or leave policy at this stage. Show eagerness to learn and contribute.