Tricentis Tosca 16.0 Released on Feb-2023 ----- UFT has been upgraded from UFT 15.0.1 to UFT One 15.0.2, Beginning at November 2020.

Thursday 29 June 2023

General Inverview Questions

Responsibilities of the Test Lead ?

Role of QA Lead includes-

  1. Manage project from initiation through closure
  2. Test planning
  3. Obtain customer acceptance of the deliverables
  4. Approve intermediate deliverables and patch releases to the client
  5. Submit effort inputs for billing
  6. Issue Management
  7. Mentoring, coaching and off-shore team management
  8. Submit reports for weekly status to the test coordinators
  9. Participating in weekly review meetings
  10. Publish KPIs for all testing projects on a weekly basis
  11. Resource mobilization for projects

What people skills should a Test Lead have?

  1. Effective and clear communication
  2. Should build good relationship with team members
  3. Good listening skills and emotional intelligence
  4. Motivate team members
  5. Resolve conflicts and ethical issues.

What makes a good test lead?


I think a good test lead is someone adaptable, detail-oriented and a good problem solver. 
  1. Adaptability can help them respond to new project requirements or navigate client requests.
  2. Attention to detail makes it easier to spot errors and ensure quality delivery.
  3. Problem-solving can help them respond to QA concerns quickly and effectively, making it possible to complete their assignments within the estimated time frame.
What will be your criteria for hiring team members?

The criteria for hiring team members are

  1. His/her technical strength is as per project requirements.
  2. His/her attitude towards the profile he will be hiring for.
  3. will he/she be a good fit with the rest of the team members

What is PDCA model?


The PDCA model stands for

  1. Plan: Identify improvements and set targets
  2. Do: Implement improvements
  3. Check: Check result of improvements
  4. Act: Learn from results

It is a Test Process Improvement (TPI) method.

PDCA is a TPI method that stands for plan, do, correct and act. 

  1. In the first stage, testers need to plan improvements and incorporate client requests into their set targets. 
  2. Then, in Do phase, they have to execute their plan, focusing on improving implementation and timeline management. 
  3. In the correct phase, testers must determine the effectiveness of their improvements by checking results and evaluating the success of their efforts. 
  4. Finally, in the act stage, testers learn from their results so they can improve their future processes and implementation strategies as they repeat the cycle.

What are some key challenges in a Testing Project ?

Key challenges of software testing include

  1. Testing phase us usually under a time constraint
  2. Understanding the requirements can sometimes be a challenge
  3. Application should be stable enough to be tested
  4. Setting priorities for testing
  5. Lack of skilled testers
  6. Regression Testing
  7. Frequent Requirements changing
  8. Lack of tools, resource, and training

 What are some risks you might encounter when testing a project?

In testing, we often encounter risks that can affect our timelines, resources, strategies and understanding of project requirements. These can create concerns, and it's important to consider them at the beginning of a project. Timeline risks can affect the project's schedule, so it's always important to be aware of potential delays. Resource risks might come from team concerns like the team's skills, experience or individual workload capabilities. Strategy risks can affect budgets and client relationships. And project requirement risks might include challenges concerning the project's scope or desired outcomes.

How do you ensure quality estimations on tests?

To ensure quality test estimations, I usually try to consider every potential factor. This includes resources, team capabilities and potential risks. I almost always give myself some extra time, that way I can exceed expectations and represent the company well to clients. Now that I'm more experienced, I have an adept sense of how long certain processes take. By considering team capabilities and needs, and always staying flexible and receptive to new information, I can ensure my estimates remain as accurate as possible.

Have you ever disagreed with a team member? How did you resolve the disagreement?

When I first started at my last company, I had a coworker who routinely approved defective work, then blamed me for the errors if the client noticed. I presented a new testing strategy to my manager, so both of our work would undergo one more approval step before we delivered it to the client. By implementing the final QA step, we could catch the errors and document their source. This helped me correct the placement of blame and, as an added benefit, it improved our ability to deliver quality work to our clients.

How would you select a Testing tool for your project ?

  1. Identify features required in an automation testing tool as per the project needs
  2. Evaluate commercial and noncommercial tools that meet the requirements
  3. Estimate cost and benefit of the tool. Cost could include licenses and training.
  4. Make the final decision in consultation with team members.
What is a Test Plan?

The Test Plan is a document describing the activities and the testing scope. It is the basic requirement for testing any software product.

What are types of the test plan?

There are three main types of Test Plan

  1. Master Test Plan
  2. Testing level specific Test Plan
  3. Testing type specific test plans

What is the Requirement Traceability Matrix ?


Requirement Traceability Matrix is linking of requirement documents to test cases. It is used for the following reason


  • To ensure that all the application requirements are tested in the verification process
  • To check Test Coverage

No comments:

Post a Comment

Note: only a member of this blog may post a comment.