What's the best piece of advice a tech leader can give when identifying software testing resources for their team?
Thank you Rahul
Excellent point Jill.
True
I believe that we cant sustain QA with Automation
Automation is next key part for QA career skill development
1. Ability to understand the requirements (do they have taste in the mouth?).
2. Attention to details.
If they know test automation, it's a big ++.
We would send UI of amazon.com or Gmail etc, UI of well-understood services and ask the candidates to come up with possible test scenarios and cases. It is quite revealing to see how superficial most of the candidates are, and also it is pleasantly surprising to see how detailed some of them are. BTW, though it appears quite cumbersome, but it is not. One can quickly figure out who is bad and good.
My best QA people over the years by far are the ones who will speak up, ask clarifying questions, point out when people in the room aren't paying attention to the details, and who hold their peers accountable to quality standards.
We do both manual and QA automation at our company, but our QA people operate more as "consultants" than people who do the majority of the QA lift. We changed our process in Q4 of last year are seeing fantastic results from the change.
The way our QA process works now, QA, devs, and product folks confer on a ticket and agree that the change they're going to make is testable, and that a basic direction on testing the change is well understood. Developers largely test their own work, manual and automated, and are expected to keep notes on what they test and how. QA reviews those notes, suggests improvements or other tests as the work is closer to completion.
We found that in our old, more traditional QA process the learning feedback loop was broken for engineers. This was especially true during periods of rapid development and for minor bugs. It was easy to say "yep, that's a bug" without digging in and figuring out how you wrote that bug and how to guard against it in the future.
With the new process, we are seeing only slightly slowed development pace, but the bug-rate in newly released code is down by 2/3rds.
Thank you
Also agree with some other points made around a person having some basic coding skills and experience!
Content you might like
We are not doing regression testing10%
25% manual, 75% automated50%
50% manual, 50% automated28%
100% manual, 0% automated8%
Don't know2%
Limited environment/Infrastructure resources31%
Inability to quickly identify the root cause of CI/CD pipeline failures45%
Lack of standardized CI/CD pipeline templates across the organization53%
Integrating security tools - inefficient security implementation leading to false positives37%
Poor communication across business and product teams/coordination challenges26%
Cost/resource management26%
Implementation of CI/CD into on-going projects and workflows22%
Internal resistance: training issues, culture, etc.14%
Inefficient implementation of CI/CD due to lack of expertise, poor training, etc.18%
Poorly written unit and acceptance testing9%
Great point!