“A lot of QA went to PM because QA was always lower.”
“I’m doing the same things I did a few years ago.”
“A new graduate can do what a senior QA does on a project.”
Do you feel the same way? I’m sure most people think so, because that’s what it looks like on the surface!
So, is it really that bad for software testers or QA?
For the opening quotes, let’s analyze them one by one.
The value of testing is undeniable. “A lot of QA goes to PM because QA is always lower.”
I don’t see the value in what QA does. On the contrary, I think the reason why QA can be changed to PM is that QA has gained a lot of training in the process of work. QA can not only be changed to PM, but also to PO, and technical QA can be changed to Dev.
In fact, QA and PM are not superior to each other, but the division of labor and responsibilities are different. QA switching to another role is not a change of status, but a better fit for them. Be proactive and do your job well, which can bring great value to the team. If done badly, the same cannot bring value. Moreover, a bad PM can affect the entire team and bring much less value than a good tester.
We should look at this problem with a cooperative mentality. The team is responsible for quality, which has always been emphasized, and everyone should have a sense of teamwork. The division of labor is only due to different interests and areas of expertise, and there is no distinction between high and low.
Quality is more and more concerned by all walks of life, quality problem can not be ignored. Software quality assurance work, software product testing of course is also very important and valuable, this point is not in doubt.
However, the value of quality is not so directly visible. Instead, the requirements person analyzes a few more requirements, the developer develops a few more function points, or writes a few more automated tests, which are obvious and seem to add more value and be recognized and valued. On the other hand, requirements validation, test design, quality status concerns, risk control, rapid discovery and problem location are not easily quantified and therefore not easily valued or respected.
Capacity building is key
“I’m doing the same things I did a few years ago.”
It’s just that the things we do seem to be the same — analyzing requirements, designing tests, testing stories, writing automated tests, etc. — that we probably did years ago and still do today. However, I believe that as long as you take everything seriously and have your own thinking and summary, it will not be the same. Such as:
For the same analysis of requirements, a few years ago, you may only see the requirements written by BA to see if there are any edges and corners missing in case; Now you can look at the rationality of the overall consideration of this demand from the perspective of industry business, whether it can bring value to users and competitiveness to enterprises. There’s a big difference between the two.
The same test story, a few years ago, may only be tested according to the acceptance criteria and some corner cases thought by myself, a story needs a day to test; Now, with your mastery of domain knowledge, technical understanding and familiarity with system functions, combined with your years of experience and increased common sense, you can probably test a feature containing several stories in half a day, or a story tested by a junior tester. You can find some problems when you take it over. This is growth, this is value!
“What a senior QA does on a project can be done by a graduate”
If you just look at what you have done, you may still stay on the surface. The person you were a few years ago is the same as you are today.
Of course, it’s important to note that a senior QA is not just about years in the job, it has to be about real ability, or it might not be as good as a good graduate.
QA’s ability to improve with age and seniority makes testing work more valuable. Therefore, the ability to improve is crucial!
So how can you improve your ability?
Ability improvement path
Seemingly the same thing, different abilities of people to do the effect is not the same. Why is he so good at solving problems? Let’s look at the process of learning to improve.
The first stage is knowledge accumulation
Knowledge points can be obtained through reading, listening to lectures, watching videos and other methods. After summarizing these points, they can become their own understanding of the knowledge.
This is the first stage of knowledge accumulation.
The second stage is experience accumulation
Carry out experiments on the learned knowledge and further apply it to practical projects to gain practical experience. Repeated practice can accumulate experience.
This stage is not enough to become a real problem solving ability.
The third stage is ability improvement
The accumulation of ability will be realized by insisting on reviewing and summarizing in practice, criticizing and improving the practice process, and applying the knowledge learned by analogy.
Thus, the transformation process from knowledge to ability is realized.
Accumulation and sharing are important
Each stage can acquire new knowledge, and then go through the same knowledge-experience-ability transformation. Continuous accumulation will realize the improvement of ability. At each stage, you can share your knowledge or experience with others, which is not only a good way to help others acquire relevant knowledge, but also a good way to improve your own ability.
Repeated changes in knowledge-experience-ability can lead to surprising results over time. It is not linear growth.
In the whole process of constantly explore their interest points, the organic combination of learning and interest, will achieve twice the result with half the effort.
Lifelong growth
Knowing how to improve your ability, it is also important to change your mindset. Here is my favorite book “Lifelong Growth”. It says there are two modes of thinking: fixed mode of thinking and growth mode of thinking. People with growth mode of thinking are more likely to succeed. We need to focus more on our own growth and less on the outside world and comparing ourselves to it.
What I said above is not only relevant to software testers, it can be applied to any role, any profession of friends, but also as quality workers, I heard many people’s concerns, I wrote this article.
Believe to accumulate much, can produce qualitative change!
Finally, let’s read more, learn more, practice more, think more, summarize more, share more, and achieve lifelong growth!
To recommend a software testing technology exchange group: 1079636098 group benefits free
If you don’t want to experience the feeling of giving up after a few days when you can’t find the materials and no one answers the questions, you can follow me to discuss with you.