Liqvid eLearning Test Engineer Interview: Rounds, Questions and Preparation

What the job involves

A Test Engineer in Indian IT services manually tests software applications, writes test cases, logs defects, and verifies fixes before release. In smaller or fast-growing firms like Liqvid eLearning, you may also help with basic automation, regression suites, and client demos. The role demands strong attention to detail, clear communication, and comfort with tools like JIRA and Selenium.

Role and Technical Knowledge

1. 1

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

   Verification checks if we are building the product right (reviews, inspections), while validation checks if we built the right product (actual testing). Give a simple example like a login page.

2. 2

   Explain the defect life cycle with the states a bug goes through.

   Cover New, Assigned, Open, Fixed, Retest, Verified, Closed, and Reopened. Mention that a tester can reject a bug as 'Not a defect' or defer it.

3. 3

   What is the difference between smoke testing and sanity testing?

   Smoke testing checks critical functionalities after a new build to decide if further testing is possible. Sanity testing checks a specific fix or small change in a stable build.

4. 4

   How would you write a test case for a simple 'Forgot Password' feature?

   List preconditions, steps, test data, and expected results. Cover valid email, invalid email, empty field, link expiry, and password reset success.

Practical Scenarios

1. 5

   You find a bug but the developer says it is not reproducible. What do you do?

   Provide detailed steps, screenshots, video, environment details, and logs. Try to reproduce on a different machine or build. Escalate to the test lead if needed.

2. 6

   How do you decide which test cases to run when you have very little time before a release?

   Prioritize based on risk and business impact. Run smoke, critical path, and high-priority regression tests. Communicate what was skipped to the lead.

3. 7

   Given a login page with username, password, and a submit button, list at least five test cases.

   Include valid login, invalid password, empty fields, SQL injection attempt, password masking, and session timeout. Mention positive and negative cases.

4. 8

   How would you test an e-learning course module that plays videos and tracks progress?

   Test video play, pause, seek, completion tracking, resume from last position, progress bar accuracy, and compatibility across browsers and devices.

Tools and Process

1. 9

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

   Test plan is a document for a specific project with scope, schedule, and resources. Test strategy is a high-level approach across projects. Test case is a set of steps for one scenario.

2. 10

   How do you use JIRA in your daily testing work?

   Create and update test cases, log defects with steps and attachments, track status, link defects to stories, and generate reports for the team.

3. 11

   Write a simple SQL query to find all users who registered in the last 7 days from a 'users' table.

   Use SELECT * FROM users WHERE registration_date >= DATE_SUB(NOW(), INTERVAL 7 DAY); Mention that exact syntax may vary by database.

4. 12

   What is the difference between functional and non-functional testing? Give examples.

   Functional tests what the system does (login, search). Non-functional tests how it performs (load, security, usability, compatibility). Give one example each.

Behavioural and HR

1. 13

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

   Use the STAR method. Describe the situation, your careful checking, the mistake you caught, and how you reported it politely with evidence.

2. 14

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

   Show interest in quality, learning different domains, and client-facing work. Mention that services exposure builds strong process discipline and teamwork.

3. 15

   How do you handle pressure when a release deadline is close and many bugs are pending?

   Stay calm, prioritize critical bugs, communicate clearly with the lead, and focus on high-risk areas first. Avoid blaming others.

4. 16

   Where do you see yourself in three years as a Test Engineer?

   Show growth from manual testing to automation or test lead roles. Mention learning Selenium, API testing, or performance testing to add value.