Testing Q&A
Manual QA testing concepts
Testing Fundamentals
Core concepts every QA professional must know for interviews.
Q1: What is Software Testing?
Software testing is the process of evaluating and verifying that a software application functions correctly, meets specified requirements, and is free of defects.
Interview Tip
Always emphasize that testing is not just about finding bugs - it’s about ensuring the software meets user expectations and business requirements.
Q2: What are the different levels of testing?
Testing Levels
1. Unit Testing
- Test individual components/modules in isolation
- Usually done by developers
- Fastest and cheapest to fix defects
2. Integration Testing
- Test interaction between integrated modules
- Types: Big Bang, Top-down, Bottom-up, Sandwich
3. System Testing
- Test complete integrated system
- Verify system meets specified requirements
- End-to-end functionality testing
4. Acceptance Testing
- Final testing before release
- Types: User Acceptance Testing (UAT), Business Acceptance Testing (BAT)Q3: Functional vs Non-functional Testing
Comparison
Functional Testing | Non-functional Testing
----------------------------+---------------------------
Tests WHAT the system does | Tests HOW the system performs
Validates business requirements | Validates system characteristics
Input → Process → Output | Performance, security, usability
Examples: Login, payments | Examples: Load testing, securityQ4: Verification vs Validation
Q5: Software Testing Life Cycle (STLC)
STLC Phases
1. Requirement Analysis
└─ Understand and analyze requirements, identify testable requirements
2. Test Planning
└─ Create test strategy and plan, estimate effort and resources
3. Test Case Development
└─ Write detailed test cases, prepare test data
4. Environment Setup
└─ Configure test environment, set up test data
5. Test Execution
└─ Execute test cases, log defects
6. Test Closure
└─ Test completion report, lessons learnedQ6: Test Case vs Test Scenario
Comparison
Test Case | Test Scenario
-----------------------------------+---------------------------
Detailed step-by-step instructions | High-level functionality to test
Specific input values and results | One-liner description
Example: "Enter username 'admin', | Example: "Verify user login
password '123', click login, | functionality"
verify dashboard appears" |Q7: What is Regression Testing?
Testing existing functionality after changes to ensure new code doesn’t break working features.
Full Regression
Test entire application
Partial Regression
Test affected areas only
Q8: Smoke vs Sanity Testing
Comparison
Smoke Testing | Sanity Testing
----------------------------------+----------------------------------
Wide and Shallow | Narrow and Deep
Tests basic functionality | Tests specific functionality
Build acceptance testing | Subset of regression testing
"Can we proceed with testing?" | "Is the specific fix working?"Q9: What is Exploratory Testing?
Simultaneous learning, test design, and test execution without predetermined test cases.
When to Use
Best used when requirements are unclear, time is limited, or when looking for usability issues that scripted tests might miss.
Test Design & Execution
Creating effective test cases and ensuring thorough test coverage.
Q10: How to Write a Good Test Case?
Test Case Template
Test Case ID: TC_001
Test Scenario: User Login
Pre-conditions: User account exists
Test Steps:
1. Navigate to login page
2. Enter valid username
3. Enter valid password
4. Click login button
Expected Result: User redirected to dashboard
Post-conditions: User logged in successfully
Priority: High
Test Data: Username: testuser@email.com, Password: Test123!Best Practices
- Use action verbs (Click, Enter, Verify)
- Include specific test data
- Write from user perspective
- Keep steps simple and atomic
Q11: How to Ensure Complete Test Coverage?
Q12: How to Prioritize Test Cases?
Priority Levels
P0 - Critical: Blocker issues that prevent core functionality
P1 - High: Major functionality that impacts business
P2 - Medium: Important features with moderate impact
P3 - Low: Nice to have featuresDefect Management
Bug lifecycle, reporting, and handling disagreements.
Q13: What is the Defect Life Cycle?
Defect States
New → Assigned → Open → Fixed → Retest → Verified → Closed
Alternative paths:
- New → Rejected (not a valid defect)
- Fixed → Reopened (issue persists)
- Open → Deferred (fix postponed)
Stage Descriptions:
- New: Defect reported by tester
- Assigned: Assigned to developer
- Open: Developer working on fix
- Fixed: Developer completed fix
- Retest: Ready for testing
- Verified: Fix confirmed working
- Closed: Defect resolvedQ14: What to Include When Raising a Bug?
Bug Report Template
Bug ID: BUG_001
Summary: Login fails with valid credentials
Description: User cannot login with correct username/password
Severity: High | Priority: High
Environment: Windows 10, Chrome 96.0
Steps to Reproduce:
1. Navigate to login page
2. Enter username: test@email.com
3. Enter password: Test123!
4. Click Login button
Expected Result: User should be logged in
Actual Result: Error message "Invalid credentials"
Screenshots: [attachment]
Reporter: John Doe
Date: 2024-01-15Q15: Severity vs Priority
Comparison
Severity (Impact on functionality) | Priority (Business urgency)
-----------------------------------+----------------------------
Technical assessment | Business decision
High: System crash | High: Must fix immediately
Medium: Feature not working | Medium: Fix in current release
Low: UI cosmetic issues | Low: Fix in future releaseQ16: Handling Developer Disagreement
Question
How do you handle a situation where a developer disagrees with your bug?
Remember
The goal is to deliver quality software, not to be “right”. Stay objective and collaborative.
Agile & Process
Agile methodology, sprints, and QA responsibilities.
Q17: Your Role in Agile Sprint
Sprint Phases
Sprint Planning:
- Participate in story estimation
- Understand acceptance criteria
- Plan testing approach
During Sprint:
- Write test cases early
- Collaborate with developers
- Perform continuous testing
- Attend daily standups
Sprint Review/Retrospective:
- Demo tested features
- Share testing insights
- Suggest improvementsQ18: What is a User Story?
Example
As a bank customer,
I want to check my account balance online
So that I can monitor my finances without visiting the branchQ19: What is Acceptance Criteria?
Conditions that must be met for user story to be considered complete.
Example
User Story: Account balance check
Acceptance Criteria:
- User must be logged in
- Balance displays current amount
- Balance updates reflect recent transactions
- Error message for network issues
- Response time under 3 secondsTesting Value
Acceptance criteria directly translate to test cases and help define “Definition of Done”.
Q20: Daily Standups and QA Contribution
Tester Example
Yesterday: "Completed testing for login module, found 2 critical bugs"
Today: "Will test password reset feature and retest fixed bugs"
Blockers: "Test environment is down, need dev team support"Domain-Specific (Banking/Finance)
Testing considerations for financial applications.
Q21: Testing Banking Applications
Q22: Challenges in Finance Module Testing
Critical Note
Financial applications require extra attention to data accuracy, security vulnerabilities, and regulatory compliance. Any bug in production can have serious financial and legal consequences.
Q23: Security Testing in Banking Apps
Scenario-Based Questions
Real-world situations and how to handle them.
Q24: Handling Unclear Requirements
Pro Tip
Never assume! It’s better to ask questions and look thorough than to test the wrong functionality.
Q25: Testing with Limited Time
Time-boxed Strategy (2 hours)
30 min: Smoke testing (basic flows)
60 min: Critical business scenarios
30 min: Exploratory testing on new featuresQ26: Handling Production Bugs
Production Bug Response
Speed and accuracy are crucial. Document everything, communicate clearly, and focus on resolution first, analysis second.
Q27: How to Test a Login Page?
Sample Test Cases
TC_001: Valid login
Steps: Enter valid username/password, click login
Expected: Redirect to dashboard
TC_002: Invalid password
Steps: Enter valid username, invalid password, click login
Expected: Error message "Invalid password"
TC_003: Account lockout
Steps: Enter wrong password 3 times
Expected: Account locked for security
TC_004: SQL Injection attempt
Steps: Enter "admin'; DROP TABLE users;--" as username
Expected: Input sanitized, login fails safelyInterview Success Tips
Final Preparation Checklist
- Review testing fundamentals - STLC, test levels, types
- Practice test case writing - Clear, concise, traceable
- Understand defect lifecycle - States, severity vs priority
- Know Agile methodology - User stories, acceptance criteria
- Prepare domain examples - Banking, e-commerce, healthcare
- Practice scenario-based answers - STAR method