Manually SQA Testing Interview Question

1. What is testing and why is it important?

Testing ka matlab hai software ki quality ko evaluate karna taake ye dekha ja sake ke product
requirements ko pura kiya gaya hai. Iski ahmiyat is liye hai kyunki ye bugs aur defects ko
identify karta hai, jo final product ki quality aur user experience ko behtar banata hai.

2. What are the phases of the Software Development Life Cycle (SDLC)?

SDLC ek process hai jisme software develop hota hai. Iske main phases hain:

● Requirement Gathering: User aur stakeholders se requirements ikattha karna.

● Design: Software architecture aur design tayyar karna.
● Implementation: Code likhna.
● Testing: Software ko test karna.
● Deployment: Software ko production environment mein deploy karna.
● Maintenance: Software ki updates aur bugs fix karna.

3. What are the phases of the Software Testing Life Cycle (STLC)?

STLC testing process ko manage karne ke liye use hota hai. Iske phases hain:

● Requirement Analysis: Testing requirements ko samajhna.

● Test Planning: Testing strategy aur scope tayyar karna.
● Test Case Development: Test cases likhna.
● Test Environment Setup: Testing ke liye environment tayyar karna.
● Test Execution: Test cases ko run karna.
● Test Closure: Testing activities ko finalize karna.

4. What is a Test Plan and what does it include?

Test Plan ek document hai jo testing process ka overview deta hai. Ismein shamil hote hain:

● Test objectives
● Scope of testing
● Testing approach
● Resources required
● Schedule
● Risks and mitigation strategies

5. What is a Test Case and what is its writing format?

Test Case ek document hai jo specific conditions aur steps ko define karta hai jinhein test karna
hota hai. Iski format mein shamil hote hain:

● Test Case ID
● Description
● Pre-conditions
● Test Steps
● Expected Results
● Actual Results
● Status (Pass/Fail)

6. What is the difference between Positive and Negative Testing?

● Positive Testing: Ye testing ka process hai jisme valid inputs diye jate hain taake ye
check kiya ja sake ke software expected results de raha hai.
● Negative Testing: Ye testing ka process hai jisme invalid inputs diye jate hain taake ye
dekha ja sake ke software unhe sahi se handle kar raha hai.

7. What is the Defect Life Cycle?

Defect Life Cycle wo stages hain jinke zariye ek defect ya bug guzarta hai, jese:

1. New
2. Assigned
3. Open
4. Fixed
5. Retested
6. Closed
7. Reopened (agar issue resolve nahi hua)

8. What is Bug Reporting and what details should it contain?

Bug reporting ka matlab hai defects ko track aur document karna. Ismein shamil hone chahiye:

● Bug ID
● Summary
● Description
● Steps to reproduce
● Environment
● Severity and priority
● Status
● Screenshots

9. What is Regression Testing and why is it important?

Regression Testing purani functionalities ko check karne ke liye ki jati hai taake ye ensure kiya
ja sake ke naye code changes ne purani features ko affect nahi kiya. Iski ahmiyat ye hai ke ye
bugs ko identify karne mein madad karta hai jo naye changes se aa sakte hain.

10. What is Usability Testing?

Usability Testing ka matlab hai software ki user-friendliness aur usability ko test karna. Ismein
dekha jata hai ke user ka experience kaisa hai aur kya software asan hai istemal karne ke liye.

11. What is Exploratory Testing and when should it be used?

Exploratory Testing ek informal testing hai jisme tester bina kisi predefined test case ke software
ko explore karta hai. Ye uss waqt use hoti hai jab requirements unclear ho ya jab time limited
ho.

12. What is the difference between Test Automation and Manual Testing?

● Manual Testing: Ye testing ka process hai jisme testers manually test cases run karte
hain bina kisi automation tool ke.
● Test Automation: Ye testing ka process hai jisme automation tools use hote hain test
cases ko execute karne ke liye, jo time-saving aur repeatable hota hai.

13. What are Boundary Value Analysis and Equivalence Partitioning?

● Boundary Value Analysis: Ye technique hai jisme input ke boundary values ko test kiya
jata hai, jaise minimum aur maximum values.
● Equivalence Partitioning: Ye technique hai jisme input data ko classes mein divide kiya
jata hai, jahan har class ko represent karne ke liye sirf ek test case ki zarurat hoti hai.

14. What is the difference between Smoke Testing and Sanity Testing?

● Smoke Testing: Ye initial testing hai jo software ke basic functionalities ko check karta
hai taake ye ensure kiya ja sake ke build stable hai.
● Sanity Testing: Ye testing specific functionality ke changes ko verify karne ke liye hoti
hai, yeh ensure karti hai ke changes ne kisi aur functionality ko affect nahi kiya.

15. What is Functional Testing and Non-Functional Testing?

● Functional Testing: Ye software ki functionalities ko test karta hai, yani wo expected

results de raha hai ya nahi.
● Non-Functional Testing: Ye performance, security, usability, etc. jaise aspects ko test
karta hai.

16. What is Acceptance Testing and what is its purpose?

Acceptance Testing end-users ya clients dwara ki jati hai taake ye check kiya ja sake ke
software unki requirements ko fulfill karta hai. Iska purpose ye hai ke client software ko accept
kare.

17. Do you have experience with Jira or any other bug tracking tool?
How do you use it?

Jira ek popular bug tracking tool hai. Isme issues create karte hain, unhein assign karte hain,
aur unki status track karte hain. Iska use karne ke liye:

1. Issue creates karna.

2. Details fill karna (summary, description, priority).
3. Assign karna team member ko.
4. Status update karna jaise "In Progress", "Resolved", "Closed".

18. What is the process of Test Case Review?

Test Case Review process mein team members test cases ko review karte hain taake ensure
kiya ja sake ke:

● Test cases complete hain.

● Requirements ko cover kar rahe hain.
● Clear aur unambiguous hain. Ye process quality improve karta hai aur defects ko pehle
hi identify kar leta hai.

19. What is Risk-Based Testing?

Risk-Based Testing wo testing approach hai jisme testing efforts ko risks ke basis par prioritize
kiya jata hai. Isme wo functionalities jinke failure se zyada impact ho sakta hai, unhein pehle
test kiya jata hai.

20. How did you track a bug and what steps did you take to resolve it?

Bug tracking process mein:

1. Bug report kiya.

2. Team ko assign kiya.
3. Bug fix kiya gaya ya not reproducible ka status diya.
4. Retest kiya aur ensure kiya ke fix successful hai.
5. Final report ke saath bug ko close kiya.
 API Testing Interview Question

1. What is API testing? Why is it important?

API testing ek process hai jisme APIs ki functionality, reliability, performance, aur security ko test
kiya jata hai. Ye is liye important hai kyunki APIs applications ke beech interaction ka bridge
hain, aur inki quality ensure karna overall application ki quality ko behtar banata hai.

2. What are the differences between API testing and UI testing?

● API Testing: Ye backend ke saath interact karta hai, inputs aur outputs ko validate karta
hai. Ye automation ke liye asan hai aur testing ka scope zyada hota hai.
● UI Testing: Ye user interface par focus karta hai, user interactions ko validate karta hai.
Ye manual testing ki zarurat zyada hoti hai aur GUI par depend karta hai.

3. What tools do you use for API testing?

● Postman: User-friendly interface ke sath APIs ko test karne ke liye.

● SoapUI: SOAP aur REST APIs dono ke liye.
● JMeter: Performance testing ke liye.
● Rest Assured: Java ke liye API testing framework.

4. Explain the structure of a RESTful API request.

● HTTP Method: (GET, POST, PUT, DELETE)

● Endpoint URL: Jahan request bheji ja rahi hai.
● Headers: Metadata jaise content type, authentication token.
● Body: (sirf POST aur PUT requests ke liye) Request ka data jo server ko bhejna hota
hai.

5. What is the difference between GET and POST requests?

● GET Request: Data ko retrieve karne ke liye use hota hai. Ye parameters URL mein
shamil hote hain.
● POST Request: Data create karne ke liye use hota hai. Ye body mein data send karta
hai aur server par changes laata hai.

6. How do you handle authentication in API testing?

Authentication handle karne ke liye:

● API Keys: Unique keys jo request ke sath send ki jati hain.

 ● OAuth: Authorization framework jo secure access deta hai.
● JWT (JSON Web Tokens): Tokens jo authentication aur user information ko secure
karte hain.

7. What is parameterization in API testing?

Parameterization ka matlab hai ke test cases ko dynamic inputs ke sath run karna, jise aap
alag-alag data sets ke sath execute kar sakte hain. Ye multiple scenarios ko validate karne mein
madad karta hai.

8. What are some common status codes in API responses?

Common HTTP status codes hain:

● 200: OK (Success)
● 201: Created (Resource successfully created)
● 400: Bad Request (Invalid request)
● 401: Unauthorized (Authentication required)
● 404: Not Found (Resource not found)
● 500: Internal Server Error (Server side error)

9. What is the role of assertions in API testing?

Assertions ka role hai ke aap response data ko validate kar sakein. Ye confirm karte hain ke API
ka response expected results ke sath match karta hai. Agar assertion fail hoti hai, to test fail
hota hai.

10. How do you validate the response of an API?

API response ko validate karne ke liye:

● Status code check karna.

● Response body ka data structure validate karna.
● Expected values ko actual values ke sath compare karna.
● Response time measure karna.

11. What is a mock API and when would you use it?

Mock API ek simulated API hai jo real API ke behavior ko replicate karta hai. Iska istemal tab
hota hai jab real API available nahi hoti ya testing ke dauran dependencies ko avoid karna hota
hai.

12. Explain the importance of API documentation.

API documentation ka matlab hai ke aapki API ka proper description hona chahiye, jo
developers ko samajhne mein madad kare. Ye endpoints, parameters, request/response
formats aur authentication methods ko detail mein explain karta hai, jo integration aur
development ko asan banata hai.

13. What is the difference between synchronous and asynchronous API

calls?

● Synchronous API Calls: Ye sequential hoti hain; ek request ka response aane tak
doosri request nahi hoti.
● Asynchronous API Calls: Ye parallel hoti hain; request bhej kar aap baaki tasks
perform kar sakte hain jab tak response nahi aata.

14. How do you test the performance of an API?

API performance testing ke liye:

● Load testing: Concurrent requests ko test karna.

● Stress testing: API ko maximum limits tak push karna.
● Response time measurement: API ka response time measure karna under different
loads.

15. What is error handling in API testing?

Error handling ka matlab hai ke aapko API errors ko identify aur handle karna hai. Ye status
codes, error messages, aur proper logging ke zariye kiya jata hai, taake aap easily issues ko
troubleshoot kar sakein.

16. How do you ensure security in API testing?

API testing mein security ensure karne ke liye:

● Strong authentication methods istemal karna.

● Data encryption (HTTPS) ko implement karna.
● Input validation aur sanitization ka istemal karna.

17. What is a SOAP API and how does it differ from a REST API?

SOAP API ek protocol hai jo XML-based messages use karta hai aur strict standards follow
karta hai. REST API lightweight hai, HTTP protocols use karta hai, aur JSON format mein data
exchange karta hai.

18. What is rate limiting and how can it affect API testing?
Rate limiting ka matlab hai ke aap API requests ki maximum number ko control karte hain. Ye
testing ke dauran ensure karta hai ke aap overload ya abuse ko prevent karein, lekin isse
testing ke results par bhi asar pad sakta hai agar requests limit tak nahi pahunchti.

19. How do you test for data integrity in APIs?

Data integrity test karne ke liye:

● Valid data inputs ko use karna aur ensure karna ke output sahi hai.
● Data consistency ko check karna, jaise ke related resources ke sath synchronization.
● Data storage aur retrieval process ko validate karna.

20. Explain how to conduct load testing on an API.

Load testing conduct karne ke liye:

● Tools jaise JMeter ya LoadRunner ka istemal karna.

● Different load scenarios create karna, jahan concurrent users simulate kiye jate hain.
● Performance metrics measure karna jaise response time, throughput, aur error rates.