Tuesday, August 31, 2021

Top 25 QA Behavioral Interview Questions & Answers



*********************************************
Top 25 QA Behavioral Interview Questions & Answers
*********************************************


1. Suppose you find a bug in production. how would you make sure that the same bug is not introduced again?
• Add uncaught functionality to regression test cases If you have Automated Regression Suite, then write a new Script which validates above functionality


2. What do you do when your developer denies that what you filed IS A BUG?
• Provide Business Documentation reference to support why the existing functionality is not as per design. 
• Involve Product Owner / Business Analyst for Discussion.
• If Bug is not reproducible then Provide Screenshots of the Bug, Give Timestamp on when you reproduced this so that Developer can check in Application Logs. 
• Provide Test Data you have used for replicating issue


3. What has been one of your greatest challenges while doing regression testing?

• Test Data issue 
• Improper selection of regression test cases might skip a major regression defect to be found


4. Difference between functional and non-functional testing?
• Functional testing verifies that features/System working as expected according to requirements,
• Nonfunctional requirements: How Well the system does it within design & resource constraints


5. Enlist some of the key challenges that are faced while performing Software Testing

• Data Issues,
 • Environment Available, 
• Using right set of tools


6. What are the different levels of testing?

• Unit Testing 
• Integration Testing 
• System Testing 
• Acceptance Testing


7.What are the drawbacks of the Agile implementation/ methodology that you faced?
• Sprints are usually very deadline constrained. 
• Documentation is not the priority 
• Frequent change in requirements


8. What is your approach when you have a high priority release to be delivered in a very short time?
• Run Automation Suites 
• . Run Unit tests. 
• Manual testing on high level Priority Business test cases


9. Give an example for High Priority Low Severity Bug
• Wrong Logo Image in Application


10. What is your understanding regarding a Test plan?

• Test plan is a document that consists of scope, approach, resources, and outline of the testing project as well as the activities for tracking the progress of the project.


11. Explain what will be your reaction if a project you had been working got Sudden change in its deadline?
• As a QA Engineer, Be open on your thoughts if you can deliver the project with QA Sign off covering all testcases 
• If Pre release is must, then discuss the opportunities of increasing QA Resources or possibility of partial product delivery 
• You have the power to hold QA Sign off if you are not satisfied with quality of product which eventually stops the release date


12.What is the difference between Smoke testing and Sanity Testing?
• Sanity testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes.
• Smoke Testing is a special type of testing performed on Software build to check the critical functionalities of the program


13. Differentiate Ad-hoc Testing and Exploratory Testing?
• Adhoc testing Includes learning the application first and then proceeding with the testing process. 
• Exploratory testing form of testing includes learning the application while testing.


14.What are your daily activities as a member of automation tester in your office?
• Running Smoke Suite on daily Basis and sending the mail to team on health of the application 
• Verify Defects Assigned to you and take appropriate Actions 
• Working on Manual and Automation testing for the stories in Current Sprint


15.How do you select regression test cases or form the regression test suite?

• Include the test cases that verify core features of the application:
• Include the test cases for functionalities that have undergone recent changes:
• Include the test cases that have frequently yielded bugs:


16. Have you ever managed writing the test cases without having any documents?
In one of my previous project, we had to redevelop our internal tool with  new Technology, But There are no testcases/Documentation for the old/existing product. As there is no documentation, Below are the steps have followed
• Understand and exploring the existing Product to come up with Scenarios.
• Spending time with Product owner or Seniors to understand the Business of the tool.
• Going through production Bugs which found previously for product so that edge testcases are not missed in writing the tests for Upgraded product


17. What is the first action you perform as a tester when application throws any weird Errors?
• Open Developer tools-> Check in Console for any Java Script Errors 
• Open Network Tab -> And see if any request Responses are failed • Verify Application logs to understand the actual issue


18. How do you solve if there is any conflict with your peer QA on any technical aspect?
• There should be argument only up to certain extent with your Peer on why you are correct 
• If it is still conflict, 
• Involve team and discuss the conflict issue with larger Audience. Open to take suggestions from your Team. 
• Accept any decision made from Team meeting with Smile.


19. How do you solve if there is any conflict with your peer QA on any technical aspect?
• There should be argument only up to certain extent with your Peer on why you are correct 
• If it is still conflict, 
• Involve team and discuss the conflict issue with larger Audience. Open to take suggestions from your Team. 
• Accept any decision made from Team meeting with Smile.


20. How do we decide if test case Is not ideal candidate for Automation?

• Tests which are highly dependent on Data with frequent changes every time 
• Tests which cannot be automated due to technical challenges 
• Tests which are unstable due to complex nature of Application.


21. Difference between retesting and regression testing?
• Retesting is done to make sure that the tests cases which failed in last execution are passed after the defects are fixed. 
• Regression testing is to ensure that changes have not affected unchanged part. 
• Regression testing is not carried out for specific defect fixes


22. What's the most interesting bug that you've found recently?
Mention the unique bug which you could detect which shows the huge impact on the System.

23. In Agile Environments, in case you have any doubts regarding your project, how do you approach?

• As a tester, For Domain related queries, You should reach out to Business Analyst, Product Owner


24. How Will You Tell If Enough Test Cases Have Been Created To Test A Product?
• Each Business requirement is mapped to at least one test Scenario 
• Each Test Scenario should have positive and negative test cases 
• Using traceability Metrix to check whether these testcases are covering all the requirement specification

2 comments:

How to install Java on EC2

***************************************** How to install Java on EC2 ***************************************** To be continued, In this post...

All Time Popular Post