Skip to main content

QA Lead or Manager Interview Questions

Displaying 1 - 10 of 25

What Are The Points That Are Covered In The Planning Phase Of Automation?

During the planning phase of automation, the points to be considered are as follows:

  • Selection of the “right” Automation tool
  • Selection of Automation Framework if required
  • List of in scope and out of scope items for automation
  • Test Environment Setup
  • Preparing the Gantt Chart of Project timelines for test script development & execution.
  • Identify Test Deliverables

Is Automation Testing A Complete Replacement For Manual Software Testing?

No. Proper automation requires as little intervention from humans as possible since the tools used are built to run tests once they are set up. As convenient as this might be, it should not be a complete replacement for manual testing – only for repetitive tasks like load testing, where thousands of virtual users are required.  

Engineers should not automate things like test scripts if those scripts can only be expected to run occasionally, nor should they automate code reviews, or bug testing for new builds of software that might require human interaction to detect issues. We can conclude by saying that large-scale, repetitive tasks are a better fit for automation.

What Are The Pre-requisites To Start Automation Testing?

The first step is to segregate the different test cases that are to be automated. Following this, you must prepare test data as per the needs of the test cases. Reusable functions need to be written which are frequently used in those test cases. Later test scripts are prepared by using reusable functions and applying loops and conditions wherever necessary.

How will you manage Team Conflicts?

With the diversity in backgrounds and working styles of team members, the first step is to expect and prepare for conflicts during the test project.

The next step is to hold a meeting and appraise team members of the project status. The Test Manager needs to keep communication open for everyone such that the team frustrations and anger are vented out. Lastly, ask the team members to co-operate and stress the importance of their cooperation for the success of the project.

Mention some of the best practices for test estimation?

Some of the best practices for Test Estimation are:

  • Add some buffer time: Having a buffer time is always an advantage, it may help to deal with a delay caused due to unexpected reason like talented member quits the job suddenly.
  • Account resource planning in estimation: Make sure that your estimation is realistic and considered crucial factors like availability of human resource.
  • Use the past experience reference: Through your past experience try to avoid all the obstacles or possible hindrance that are most likely to happen.
  • Stick to your estimation: Estimation is not full proof. It may go wrong also. In the early phase of the project, you should re-check the test estimation and if required make modifications as well.

What is three-point estimation?

In the three-point estimation, three values are initially produced for every task based on previous experience. For example, to complete a specific task the different possibilities are:

  • Best case estimate: 120 man-hours or 15 days with experienced team members
  • The most likely estimate: 170 hours or 21 days with enough resources and moderate team members experience
  • The worst-case estimate: 200 man-hours or 25 days and with a team that has lesser work experience
Subscribe to QA Lead or Manager Interview Questions

About

At ProgramsBuzz, you can learn, share and grow with millions of techie around the world from different domain like Data Science, Software Development, QA and Digital Marketing. You can ask doubt and get the answer for your queries from our experts.