Complete Software Testing Interview Refresher
Guide
Fundamentals to Advanced Topics for QA / SDET / Automation /
API / ETL Interviews
1. Introduction to Software Testing
What is Software Testing?
Software Testing is the process of verifying and validating that a software application:
• works as expected
• meets business requirements
• is defect-free
• delivers quality user experience
Testing helps identify:
• defects
• gaps
• missing requirements
• performance issues
• security vulnerabilities
Why Testing is Important
Testing ensures:
• software reliability
• product quality
• customer satisfaction
• risk reduction
• stable production releases
Without testing:
• production failures increase
• customer trust decreases
1
• business impact becomes severe
QA vs QC vs Testing
Quality Assurance (QA)
Process-oriented. Focuses on improving development/testing processes.
Example:
• process improvements
• standards
• reviews
Quality Control (QC)
Product-oriented. Focuses on identifying defects.
Example:
• executing test cases
• defect validation
Testing
Actual execution and verification activity.
Verification vs Validation
Verification
“Are we building the product right?”
Static activity:
• reviews
• walkthroughs
• inspections
2
Validation
“Are we building the right product?”
Dynamic activity:
• execution
• testing application behavior
SDLC (Software Development Life Cycle)
Stages: 1. Requirement Gathering 2. Analysis 3. Design 4. Development 5. Testing 6. Deployment 7.
Maintenance
STLC (Software Testing Life Cycle)
Stages: 1. Requirement Analysis 2. Test Planning 3. Test Case Design 4. Test Environment Setup 5. Test
Execution 6. Defect Reporting 7. Test Closure
Software Testing Principles
ISTQB 7 Principles
1. Testing shows presence of defects, not absence
2. Exhaustive testing is impossible
3. Early testing saves cost
4. Defects cluster together
5. Pesticide paradox
6. Testing depends on context
7. Absence of errors fallacy
2. Types of Testing
Functional Testing
Verifies business functionality.
3
Examples:
• login
• payments
• user workflows
Unit Testing
Performed by developers.
Tests:
• individual methods/functions
Tools:
• JUnit
• NUnit
Integration Testing
Tests interaction between modules.
Examples:
• frontend + backend
• API + DB
System Testing
Tests complete application end-to-end.
User Acceptance Testing (UAT)
Performed by business/users.
Validates:
• business expectations
4
Smoke Testing
Checks critical functionality after build deployment.
Purpose:
• determine if build is stable
Sanity Testing
Checks specific functionality after minor changes.
Regression Testing
Ensures existing functionality is not broken after changes.
Very important in Agile.
Retesting
Testing fixed defects again.
Non-Functional Testing
Performance Testing
Measures:
• speed
• stability
• scalability
Load Testing
Checks behavior under expected user load.
5
Stress Testing
Checks behavior beyond capacity limits.
Spike Testing
Sudden increase/decrease in users.
Volume Testing
Tests large data volumes.
Endurance/Soak Testing
Tests long-duration stability.
Security Testing
Verifies:
• vulnerabilities
• authentication
• authorization
• data protection
Common areas:
• SQL Injection
• XSS
• CSRF
• Broken Authentication
Tools:
• OWASP ZAP
• Burp Suite
6
Usability Testing
Checks:
• user friendliness
• navigation
• accessibility
Compatibility Testing
Tests:
• browsers
• devices
• operating systems
Accessibility Testing
Ensures support for disabled users.
Examples:
• screen readers
• keyboard navigation
Localization Testing
Checks application for:
• languages
• region formats
• currencies
Internationalization Testing
Ensures software supports multiple regions/languages.
7
3. Agile Testing Concepts
Agile Methodology
Agile focuses on:
• iterative delivery
• continuous feedback
• collaboration
Scrum Terminologies
Sprint
Fixed iteration cycle.
Usually:
• 2 weeks
• 3 weeks
Product Backlog
List of requirements/features.
Sprint Backlog
Features selected for sprint.
Daily Standup
Short daily status meeting.
Retrospective
Discussion for improvements.
8
Role of QA in Agile
QA participates in:
• requirement analysis
• sprint planning
• test design
• automation
• regression
• release validation
Shift Left Testing
Testing early in SDLC.
Benefits:
• lower defect cost
• faster feedback
• better quality
Continuous Testing
Testing integrated into CI/CD pipeline.
4. Defect Management
Defect Life Cycle
Stages: 1. New 2. Assigned 3. Open 4. Fixed 5. Retest 6. Closed 7. Reopened
9
Severity vs Priority
Severity
Impact of defect technically.
Examples:
• crash
• data loss
Priority
Urgency to fix.
Defect Report Should Include
• summary
• steps
• expected result
• actual result
• screenshots
• logs
• environment details
Root Cause Analysis (RCA)
Identifying actual reason behind defects.
5. Test Design Techniques
Black Box Testing
Tests functionality without code knowledge.
10
Equivalence Partitioning
Divide inputs into valid/invalid groups.
Boundary Value Analysis
Focus on edge values.
Example: Range 1–100 Test: 0,1,100,101
Decision Table Testing
Used for business rules.
State Transition Testing
Used when behavior changes by state.
Example: ATM states
Error Guessing
Experience-based testing.
White Box Testing
Tests internal code logic.
Includes:
• statement coverage
• branch coverage
• path coverage
11
Grey Box Testing
Combination of black + white box.
6. API Testing
What is API Testing?
Validating backend services without UI.
Checks:
• request
• response
• status codes
• data validation
Common HTTP Methods
GET → retrieve data
POST → create data
PUT → update data
DELETE → remove data
Important Status Codes
200 → success
201 → created
400 → bad request
401 → unauthorized
403 → forbidden
404 → not found
500 → server error
12
API Validation Areas
• response body
• status codes
• schema validation
• authorization
• performance
• error handling
Tools
• Postman
• REST Assured
• Swagger
REST vs SOAP
REST
• lightweight
• JSON based
SOAP
• XML based
• protocol heavy
JSON Basics
Common structures:
• objects
• arrays
• key-value pairs
13
Authentication Types
• Basic Auth
• Bearer Token
• OAuth
• JWT
7. Database / ETL Testing
What is ETL Testing?
Validating:
• Extract
• Transform
• Load
processes.
ETL Validation Areas
• source-to-target validation
• data completeness
• duplicate checks
• null validation
• transformation validation
SQL Concepts
Joins
INNER JOIN
Matching records.
14
LEFT JOIN
All left table records.
RIGHT JOIN
All right table records.
FULL JOIN
All records from both tables.
SQL Queries
Common Queries
SELECT
WHERE
GROUP BY
HAVING
ORDER BY
COUNT
SUM
AVG
Important SQL Concepts
• Primary Key
• Foreign Key
• Index
• Constraints
• Stored Procedures
• Views
Data Validation Techniques
• row count validation
15
• duplicate validation
• null checks
• reconciliation testing
Backend Testing
Validates:
• DB updates
• stored procedures
• data consistency
8. Automation Testing
Why Automation?
Benefits:
• faster execution
• repeatability
• regression coverage
• CI/CD integration
Automation Framework Components
• test scripts
• locators
• reusable functions
• reporting
• configuration
Selenium Basics
Used for browser automation.
16
Selenium Components
• WebDriver
• WebElement
• Locators
Types of Locators
• id
• name
• xpath
• css selector
• class name
XPath
Absolute XPath
Starts from root.
Relative XPath
Preferred flexible approach.
Waits in Selenium
Implicit Wait
Global wait.
Explicit Wait
Conditional wait.
Preferred.
17
TestNG Concepts
• annotations
• assertions
• grouping
• parallel execution
Maven
Dependency management tool.
Page Object Model (POM)
Separates:
• locators
• actions
• test logic
Improves maintainability.
Data-Driven Testing
Uses external test data.
Examples:
• Excel
• CSV
• JSON
BDD (Behavior Driven Development)
Uses:
• Given
• When
• Then
18
Tools:
• Cucumber
9. CI/CD Concepts
Continuous Integration
Code merged frequently.
Automated:
• build
• tests
Continuous Delivery
Application always release-ready.
Continuous Deployment
Automatic production deployment.
Jenkins
Popular CI/CD tool.
Used for:
• builds
• automation execution
• scheduling
19
Git Basics
Common Commands
git clone
git add
git commit
git push
git pull
Branching
Used for:
• feature development
• bug fixes
Merge Conflicts
Occurs when same code changes overlap.
10. Performance Testing Concepts
JMeter Basics
Used for:
• load testing
• performance testing
Important Metrics
• response time
• throughput
• TPS
• latency
20
• CPU usage
Bottleneck
System limitation reducing performance.
11. Security Testing Concepts
Common Vulnerabilities
SQL Injection
Malicious SQL query execution.
Cross Site Scripting (XSS)
Injecting malicious scripts.
CSRF
Unauthorized actions through authenticated users.
OWASP Top 10
Important security risks list.
12. Mobile Testing
Types
• Native apps
• Web apps
• Hybrid apps
21
Mobile Validation Areas
• gestures
• orientation
• notifications
• battery usage
• network switching
13. Cloud & Modern Testing Concepts
Cloud Testing
Testing applications deployed in cloud environments.
Examples:
• AWS
• Azure
• GCP
Microservices Testing
Validates:
• independently deployed services
• API communication
Contract Testing
Ensures API contracts remain valid.
22
Containerization
Docker
Application packaging tool.
Kubernetes
Container orchestration platform.
14. AI in Software Testing
AI-Assisted Testing
Using AI tools to improve:
• test creation
• documentation
• debugging
• productivity
AI Use Cases in QA
• automated test case generation
• defect summarization
• test data generation
• requirement analysis
• automation script assistance
Prompt Engineering for QA
Writing effective prompts for:
• test scenarios
• edge cases
• SQL queries
• automation help
23
AI Limitations
AI cannot fully replace:
• business understanding
• exploratory testing
• critical thinking
• risk analysis
15. Important Interview Questions
Manual Testing
• Difference between severity and priority?
• What is regression testing?
• Explain STLC.
• Explain defect lifecycle.
• What is smoke testing?
API Testing
• Difference between PUT and POST?
• What is status code 401?
• How do you validate APIs?
• Difference between REST and SOAP?
SQL / ETL
• Difference between WHERE and HAVING?
• Explain joins.
• How do you validate ETL?
• How do you find duplicates?
Automation
• What is Selenium?
24
• Difference between implicit and explicit wait?
• Explain POM.
• Explain TestNG annotations.
Agile
• What happens in sprint planning?
• Explain shift-left testing.
• Role of QA in Agile?
AI-Related Questions
• How are you using AI in QA?
• Can AI replace testers?
• How can AI improve productivity?
• What are risks of AI-generated testing?
16. Strong Interview Tips
During Interviews
Speak Structured Answers
Use:
• definition
• example
• practical usage
Explain Real Project Experience
Recruiters value:
• practical examples
• production scenarios
more than textbook definitions.
25
Show Problem Solving
Focus on:
• defect identification
• debugging
• validation approach
Mention AI Carefully
Good: “I use AI tools to accelerate test case generation and improve productivity.”
Avoid: “I fully automate everything using AI.”
17. Modern Testing Trends
Important Topics to Know
• AI-assisted QA
• Shift-left testing
• Continuous testing
• API-first testing
• Cloud-native testing
• Test automation in CI/CD
• Microservices testing
• Observability
• Test data management
18. Final Preparation Strategy
Before Interview
Revise:
• fundamentals
• SQL queries
• API concepts
• Agile concepts
26
• defect lifecycle
• testing types
Practice:
• explaining scenarios
• bug examples
• API validation
• SQL joins
• testing workflows
Most Important Skill
Strong fundamentals + clear communication + real project examples will outperform memorized buzzwords
in interviews.
27