1. The QA Landscape: Manual Tester vs SDET for Freshers
Software Quality Assurance offers two major career tracks for entry-level candidates:
- Quality Assurance (QA) Analyst / Manual Tester: Focuses on test planning, exploratory testing, business logic verification, user experience validation, and test case execution.
- Software Development Engineer in Test (SDET) / Automation Engineer: Focuses on building automated testing suites (Selenium, Cypress, Playwright), CI/CD pipeline integration, performance testing (JMeter), and REST API automation. SDET roles command salaries of ₹6 LPA to ₹12+ LPA for freshers.
2. 3-Stage QA Placement Recruitment Process
3. Black-Box Test Design Techniques (BVA & ECP)
Interviewers will ask you to derive test cases for a specific input field (e.g., an age input accepting 18 to 60 years).
1. Equivalence Class Partitioning (ECP)
Divides input data into valid and invalid partitions:
- Valid Partition: 18 to 60 (Test with 25).
- Invalid Partition 1 (Too Low): Less than 18 (Test with 12).
- Invalid Partition 2 (Too High): Greater than 60 (Test with 75).
- Invalid Partition 3 (Data Type): Non-numeric characters (Test with "abc" or special characters).
2. Boundary Value Analysis (BVA)
Bugs occur overwhelmingly at boundaries. For range $[A, B]$, test $A-1, A, A+1$ and $B-1, B, B+1$:
- For range $[18, 60]$, test cases are: 17, 18, 19 and 59, 60, 61.
4. Selenium WebDriver & Page Object Model (POM) Blueprint
Page Object Model (POM) is the industry standard design pattern where web pages are represented as classes and elements are encapsulated:
5. Top 15 QA Interview Questions & Model Answers
Q1: What is the core difference between Verification and Validation?
Answer:
- Verification (Static Testing): "Are we building the product right?" Evaluates documents, architecture, code reviews, and inspections without executing the application code.
- Validation (Dynamic Testing): "Are we building the right product?" Verifies that the software satisfies specified user requirements by executing test cases on the live build.
Q2: What is the difference between Smoke Testing and Sanity Testing?
Answer:
- Smoke Testing (Build Verification Test): Shallow and wide testing performed on an initial software build to verify that critical baseline features (like login, dashboard loading) are functioning before accepting the build for deep testing.
- Sanity Testing: Narrow and deep testing performed on a stable build after a defect fix to verify that the specific bug was resolved and adjacent features were not broken.
Q3: What is the difference between Severity and Priority? Give examples.
Answer:
- Severity: The technical impact of the defect on system operation (Critical, High, Medium, Low). Defined by QA.
- Priority: The business urgency of resolving the defect (High, Medium, Low). Defined by Product Manager/Lead.
- High Severity & Low Priority: An edge-case crash on legacy Windows 7 operating systems that only 0.01% of users run.
- Low Severity & High Priority: The company's brand logo is misspelled or broken on the public landing page.
Q4: What is the difference between `driver.close()` and `driver.quit()` in Selenium?
Answer: driver.close() closes only the current active browser window/tab that WebDriver currently has focus on. driver.quit() terminates the entire WebDriver session, closing all open windows and killing the associated browser driver process.
6. Defect Life Cycle & Jira Best Practices
When you find a bug in manual or automated testing, follow the standard life cycle:
Key Elements of a Professional Bug Report in Jira:
- Summary: Clear, concise title indicating what failed where (e.g., "[Checkout] Clicking Place Order with empty CVV triggers 500 error instead of validation").
- Preconditions: User role, browser version, authenticated session state.
- Steps to Reproduce: Exact numbered steps to replicate the defect 100% of the time.
- Expected Result vs Actual Result: Clear contrast of what should have happened versus what occurred.
- Attachments: Screenshots with highlights, network HAR log, or browser console stack trace.