General QA Interview Questions

Hinglish
1. Tell me about yourself as a QA Engineer.
English:
I am a QA Engineer with experience in both Manual and Automation Testing. I have worked with Selenium using Java, TestNG, and Maven. My responsibilities include writing test cases, executing them, reporting defects, and creating automation scripts.

Hinglish:
Main ek QA Engineer hoon aur mujhe Manual aur Automation dono ka experience hai. Maine Selenium, Java, TestNG aur Maven ke saath kaam kiya hai. Meri responsibilities me test cases likhna, execute karna, defect report karna aur automation scripts banana shamil hai.
2. Tell me about your project and testing workflow.
English:
I am working on an E-commerce project where we test the end-to-end flow like Login, Product Search, Cart, and Payment. We use Agile methodology and Jira for bug tracking. For automation, we follow Page Object Model (POM).

Hinglish:
Main E-commerce project par kaam kar raha hoon jisme hum end-to-end flow test karte hain jaise Login, Search, Cart aur Payment. Hum Agile methodology aur Jira use karte hain. Automation ke liye hum Page Object Model (POM) follow karte hain.
3. What are your day-to-day Roles & Responsibilities?
English:
1. Understanding User Stories & Requirements
2. Writing & Executing Test Cases in TestRail / Excel
3. Defect Reporting & Tracking in JIRA
4. Automation Scripting & Framework Maintenance
5. Attending Daily Stand-ups & Sprint Ceremonies

Hinglish:
1. Requirements aur User Stories samajhna
2. Test cases likhna aur execute karna
3. Bug report karna aur JIRA me track karna
4. Automation script banana aur maintain karna
5. Daily Scrum call attend karna
4. How do you raise a defect/bug in JIRA?
English:
1. Click on Create Issue
2. Select Issue Type as Bug
3. Enter Summary and Description
4. Add clear Steps to Reproduce
5. Mention Expected vs Actual Result
6. Attach Screenshot or Logs
7. Assign Priority & Severity then click Submit

Hinglish:
Jira me defect raise karne ke steps:
1. Create Issue par click karo
2. Issue Type = Bug select karo
3. Summary aur Description likho
4. Steps to reproduce add karo
5. Expected aur Actual result likho
6. Screenshot attach karo
7. Submit karo
5. What is the difference between Smoke and Sanity testing?
English:
Smoke Testing: Performed on initial build to verify critical core functionality.
Sanity Testing: Performed on a stable build after a bug fix to verify specific features.

Hinglish:
Smoke: Nayi build aate hi basic critical cheezein check karna.
Sanity: Bug fix hone ke baad usi feature ko detail me recheck karna.
6. Explain the Defect / Bug Life Cycle.
English:
The journey of a defect from discovery to closure: 1. New, 2. Assigned, 3. Open, 4. Fixed, 5. Retest, 6. Verified, 7. Closed.

Hinglish:
Bug jab milta hai to New, fir senior use dev ko Assign karta hai, dev use theek karke Fixed bolta hai, tester fir use Retest karta hai aur end me Closed kar deta hai.
7. Difference between SDLC and STLC?
English:
SDLC (Software Development Life Cycle): Covers the entire process of software creation from requirement collection to deployment.
STLC (Software Testing Life Cycle): Focuses strictly on testing phases: Requirement Analysis, Test Planning, Test Case Design, Execution, Bug Reporting, and Closure.

Hinglish:
SDLC: Pura software banane ka process.
STLC: Sirf testing phase ke activities ka process.

Want 33+ Advanced Manual Testing Questions?

We have compiled an extensive manual testing interview guide covering Boundary Value Analysis (BVA), Equivalence Partitioning (EP), Severity vs Priority, and Agile Jira workflows.

Explore 33+ Detailed Questions
Key Terminology

The Essential QA Glossary & Interview Student Tips

Regression Testing

Re-executing existing functional tests to verify that recent code changes or bug fixes have not broken existing functionality.

💡 Student Pro Tip: Say: "I run a targeted regression suite after every build deployment to protect core business workflows."
Exploratory Testing

Simultaneous learning, test design, and execution where testers explore the app without pre-written test cases to uncover edge-case defects.

💡 Student Pro Tip: Highlight how exploratory testing helps find unexpected bugs that scripted tests miss.
Idempotency (API Testing)

An API endpoint property where making multiple identical requests yields the exact same server state (e.g., GET, PUT, DELETE are idempotent).

💡 Student Pro Tip: Mention: "GET and PUT requests are idempotent, whereas POST creates new data each time."
RTM (Traceability Matrix)

A document mapping User Requirements to corresponding Test Cases to ensure 100% test coverage and zero missing requirements.

💡 Student Pro Tip: RTM proves to stakeholders that every requirement has been validated.
CI/CD Pipeline

Continuous Integration and Continuous Deployment. Automated pipelines (e.g., Jenkins, GitHub Actions) that build and test code on every commit.

💡 Student Pro Tip: Explain how your automated regression suite triggers automatically inside Jenkins pipelines.
Flaky Tests

Automation tests that produce both passing and failing results non-deterministically without any underlying code changes (often due to dynamic waits or timing).

💡 Student Pro Tip: Show maturity by explaining how you fix flakiness using explicit waits instead of hardcoded Thread.sleep.

Industry Best Practices for Quality Assurance

Adhering to these industry-wide guidelines ensures software stability and high-performing testing frameworks.

1. Maintain Real-time RTM

Update requirement matrices as user stories evolve in Jira to guarantee complete test coverage.

2. Early Negative Testing

Allocate 30%+ effort to negative scenarios, boundary values, and error-handling checks.

3. Clear Defect Logs

Provide developers with exact steps to reproduce, actual vs expected results, and logs to avoid bug rejections.

4. Daily Failure Audits

Analyze daily pipeline failures, quarantine flaky scripts, and refactor dynamic locators regularly.