App & Browser Testing Made Easy

Give your users a seamless experience by testing on 3000+ real devices and browsers. Don't compromise with emulators and simulators

Home Guide How to Make the Most out of your Testing Team?

How to Make the Most out of your Testing Team?

Dileep Marway, BrowserStack Champion -

First and foremost, having a clear objective on what your testing team should be doing is important. Far too often, I have gone into already set-up testing teams, and they are unsure of their objective.

What is key for me is that a tester should be curious, and they should critique the product in such a way that we give a better outcome to a customer. For instance, if we are testing a mobile app, we would not only check that the app opens but also that it is performant, it works in the background with other apps, it does not drain the battery, it does not just quit itself, the app is functional as per the requirements, the app is accessible, the list can go on.

I firmly believe that a great team succeeds only when they have a shared vision and objective.

Step One: Clear Leadership Approach

Poor-performing teams are not so because team members are poorly skilled. Rather they are poorly performing in most cases as they lack direction.

From experience, I was tasked with improving the performance output of an already established team. We had daily incidents, customers constantly complained, and delivery was consistently delayed.

The first thing I did was to see what guide rails were being put in place. Some key guide rails that I added:

  1. Testing strategy – this relates to the technology strategy and says what we are testing, why we are testing it, and what the key deliverables are.
  2. Testing approach – this would have been listed in the testing strategy as a key deliverable. This is a breakdown of the testing phases, what each entails, the entry and exit criteria for the phase, and what data is being tracked.
  3. Test exit report – this is referenced via the testing approach, though it would be a key deliverable before we can go live. This will detail the confidence levels regarding whether we can go live.

Step Two: Cultural Transformation

From experience, a testing team will do their best work when they are happy. A happy workforce has been scientifically proven to deliver a successful outcome. 

One way that I have improved the culture is first to ascertain what the level of happiness in the team is and what it is that may be making the team unhappy. 

For example, a team I worked with was unhappy as they had too much work and they had to constantly rush. This meant they were missing bugs in the product, which ultimately became escaped defects. 

In this case, we worked with our scrum masters to improve the estimation process and found that the team’s happiness improved, along with the Quality of our product.

Values are also important to ensure that behaviors in the team are accepted and behaviors that may negatively impact the work output can be removed. 

Some values that we agreed on as a team that helped us to collaborate:

  • Put the ‘Assurance’ back into ‘Quality Assurance.’
  • Ensure that we can deploy faster with HIGH Quality.
  • Ensure all our teams care about Quality.
  • Transparent QA and reporting of value.
  • Prevent bugs, don’t just find them.
  • Automate repeatable tasks and make them part of the CI/CD pipeline.
  • Automate repetitive tasks – not just for the sake of it.

Step Three: Clear Metrics For Success

Having clear metrics for success in your team will mean that the leader and team members are in unison on what ‘great’ looks like. Far too often, one person’s view of success differs from others. For this reason, agreeing on metrics that deem success means we are all working from the same sheet.

Some metrics that I have found useful for quality delivery include: tracking the level of defects found before a release goes live, then the level of escaped defects that impact our customers. For a successful delivery, I would expect the level of escaped defects to be low and the level of pre-release defects to fluctuate. Though I would expect the level of pre-release defects found to go down over time should the efficiency of our engineering team increase.

Step Four: Career Progression Frameworks

A happy and performant team is one which is growing, and personal goals are aligned with team success.

In the past, I have found that team performance is less consistent when employees do not know what they need to develop to move to the next level. 

For this reason, I made sure that there was a clear career progression framework that could be discussed on a weekly basis between leader and employee. This meant that the employee was in charge of their development and could push to get to the next level.

This approach ultimately made for a happier and more performant team.


In conclusion, it is the leader’s job to ensure they are getting the best out of their team. With the focus on a clear leadership approach; cultural transformation; clear metrics for success, and a career progression framework – there is a higher chance that your team can continue to thrive and give your customers a great quality output.

Automation Testing Champion Speaks

Featured Articles

How to build an effective Mobile Testing Strategy

Mobile Testing with Effective App Testing Tools

Curated for all your Testing Needs

Actionable Insights, Tips, & Tutorials delivered in your Inbox
By subscribing , you agree to our Privacy Policy.
thank you illustration

Thank you for Subscribing!

Expect a curated list of guides shortly.