Top 19 Test Manager Interview Questions You Must Prepare 03.Dec.2022

Some of the best practices for software Quality Assurance includes

  • Continuous Improvement
  • Documentation
  • Tool usage and experience
  • Metrics
  • Team work and shared responsibility for SQA

Most current software being tested includes distributed and multi-tier applications which can be highly complex due to the multiple dependencies among systems, hardware and servers, data communications. Therefore, testing requirements can be extensive. When time is, less a focus on integration and system can be considered.

The risk that has to be avoided while testing includes

  • Missing the deadline
  • Exceed the project budget
  • Loose the customer trust

In the three-point estimation, three values are initially produced for every task based on previous experience.

For example: to complete a specific what are the different possibilities

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 team members experience

The worst-case estimate: 200 man hours or 25 days and with a lesser work experience

Well-designed object-oriented can make it easier to trace from code to internal design to functional design to requirements.

Informal reviews are implemented many times during the early stages of the life cycle of the document. These reviews often include more people and a meeting. The purpose of the informal review is to keep the author and enhance the quality of the document. Informal reviews are not documented.

Two ways can determine the quality of test execution

Defect rejection ratio: (No. of defects rejected/ total no. of defects raised) X 100

Defect leakage ratio: (No. of defect missed/total defects of software) X 100

There are three main plan Master Test Plan, Testing level specific Test Plan and Testing type specific test plans.

Testing level test plan includes

  • Unit test plan
  • Integration test plan
  • System test plan
  • Acceptance test plan

Manual support testing: It is conducted by test team. It is a testing that includes testing of all the functions performed by the people while preparing the data and using these data from an automated

Manual scripted testing: Manual testing team does it. It is a method in which the test cases are reviewed and designed by the team before executing it.

Some of the best practices for Test Estimation is

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 important factors like availability of human resource, resource planning,

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 modification as well.

A good test report should include

  • Project Information
  • Test Objective
  • Test Summary
  • Defect

Role of QA Manager includes

  • Manage project initiation through closure
  • Test planning
  • Obtain customer acceptance on the deliverables
  • Approve intermediate deliverables and patch release to the client
  • For off-shore Testing monitor processes
  • Submit inputs for billing of effort
  • Issue Management
  • Mentoring, coaching and off-shore team management
  • Submit reports for weekly status to the test coordinators
  • Participating in weekly review meetings
  • Publish KPIs for all off-shore testing projects on a weekly basis
  • Resource mobilization for projects

Requirement Traceability Matrix is a tool that ensures that through-out the whole development process.

It is used for the following reason:

  • To know whether the development projects has met the requirements of the user
  • To meet all the requirements given by the user
  • To ensure that all the application requirement can be fulfilled in the verification process

A Beta Testing is referred when the product is going to release to the end users whereas pilot testing is referred for the product when it is in the earlier phase of the development cycle.

In beta testing application is given to a few users to ensure that application meet the user requirement and does not consist any showstopper whereas in case of pilot testing team member gives their feedback to improve the quality of the application.

While carrying out the project, mainly test manager has to estimate four things Cost, Resources, Human Skills and Time.

They can estimate the project in following ways

Work breakdown structure (WBS): Breaking down project into smaller segments

Three-point estimation: Three-point estimation is based on statistical data

Functional point method: Give weightage to each function and measure the size

Test manager must take following steps to mitigate the risk while developing product

Avoidance: Eliminate the risk factor that is involved

Reduction: Mitigate plan to decrease the impact of risks and to take correct measures

Sharing: Transfer the risk to other resource such as insource or insure

Accept: Accept the risk and prepare a plan budget for this risks

Key challenges of software testing include:

  • Always Testing should be under time constraint
  • Understanding the requirements
  • Application should be stable enough to be tested
  • Setting priorities for testing
  • Lack of skilled testers
  • Regression testing
  • Requirements changing
  • Lack of tools, resource, and training

As a QA Lead your approach should be

  • Acceptance criteria should be tightened
  • Test cases should be re-evaluated
  • More test cases should be added if possible, with equivalence class partition cases and boundary values
  • With invalid condition, more test cases should be added
  • Stop criteria required to be modified

Test plan is a document describing the activities and the testing scope. It is the basic requirement before testing any software product.