Have you wondered how to set up a QA practice from scratch? Are you joining a practice that needs a reboot?
This article will provide useful information which will help you to achieve your quality goals.
Key foundations for your practice
First and foremost, a passion for quality and understanding your users is key. Some of the best QA professionals I have seen have understood the product in and out, thus helping them to know ‘what really matters’ to users.
My first tip, get ‘user’ access to your product and use the product with a customer mindset.
Ask these key questions and feed them back to your team (including product) to improve your product:
Would you pay or be a user of this product? If not, why?
Can you meet your objective? If not, why?
Have you noticed any obstacles to meeting your objective and what are they?
Having led some large teams, what has been apparent is that no matter how big or small the team, there are some key foundational aspects that must be in place. I like to refer to a house analogy and these aspects would be the foundation.
These include:
Positive culture
A team that understands they share success and failure
The team is able to give constructive not destructive criticism
Mutual respect
A work-life balance
Check your websites and web applications in all major browsers by web testing with LambdaTest.
Having a clear strategy
Adding to our house analogy, the next key aspect is the brickwork, windows, doors, and roof to ‘build’ our house. In our QA realm, this is our ‘Testing strategy’, that covers: different types of testing which can apply to different projects, types of environments, types of testing, testing tools, and how our QA approach applies to the overarching technology department.
Adding structure to your practice
We now have our skeleton house (via our test strategy) and with our team in place the house has now been decorated. The walls have been rendered, the plumbing and electrics are all done, and the walls have been painted. We now have our awesome tenants (team).
What is now needed to be successful as a QA practice is some structure. How do we know that we are successful and we are meeting all the requirements that our user needs? Like a smoke alarm at home, that alerts when something is wrong. I like to liken this alarm to ‘escaped defects’. As a team we should track these, with our aim being to drive this down.
Based on my experience some reasons why escaped defects can be high:
Poor product understanding
Lack of structured test cases
Flaky environments and poor coding principles
Engineering and QA divide
In the above, I have listed why escaped defects can be high, but what structure (assurance) can we add to protect our customers. Relating to our house analogy I liken this to protecting our house from intruders, we may add an alarm system, blinds, etc, so people cannot see our valuables or one could even have a CCTV system.
What structure can you add to your QA practice:
Test approach — for a particular project or team/squad, we have a clear approach to what we need to test.
We know the health of our team via tracking:
Escaped defects
Test cases added
Defects found pre-release
Automated test coverage
Work with product to review our test cases and update them regularly
Test your website and web applications on multiple versions of Internet Explorer on Mac machines.
Maintaining success
Moving forward on our journey, we have a flourishing home, we are happy as a family and our smoke alarm has been nice and quiet (now that we have stopped burning the food). Back to our QA team, the escaped defects are going down — but what is important is that we can only maintain this by… enjoying what we do, and having fun!
How do we do this? We can implement:
Regular 1–2–1’s
Open door policy where staff can collaborate with their leaders
We celebrate success
We learn quickly from our mistakes
We embrace change
Perform cross browser compatibility testing on all Safari for Windows and other real browsers and operating systems.
Adding some whistles and bells
To add more to our house analogy, how can we add some extra glitz? We can automate our lighting, blinds, electrical items (like the washing machine) as an example. Likewise we can pump up our QA practice via automation.
For me automation only adds value when we know what we are automating and what value it will add. Far too many times I have seen automation for the sake of automation.
Closing, as I always say, if you have a happy team you will have a positive output. The same applies for any role. Stay happy!