Many software testers are stuck between 6K and 9K, just can’t get over 10,000. The first should be early through a lot of detours, the second is limited to this bottleneck period for a long time to rise.
So how to solve these two problems? I hope my years of experience can give you some inspiration.
This article is mainly to solve some problems of software testing practitioners’ thinking. To put it bluntly, technical problems are easy to solve, while cognitive and thinking problems are not easy to solve.
First, keep asking questions
1. Know how to solve problems after they are solved
For example, if there is a bug, you need to know what type of bug it is, what type of problem it is caused by.
2. Ask questions about unclear requirements before testing them
Don’t do it foolishly.
3. Follow up the bug modification progress
For serious bugs, track the progress of modification every day, and how long it will take.
4. Give absolute attention to problems that are difficult to reproduce
You can’t just give up because one more problem doesn’t come back.
This problem can directly lead to a great improvement in project quality. If a test is “almost”, the first leader will not be assured, and the second project quality will not be high. Such people have no hope of promotion or salary increase, and have no way to improve themselves.
Technical problems are easy to solve, but ideological problems are hard to solve
Two, reasonable control of time
1. Project cycle time
It is very important to control the project cycle time. If it is too late, arrange some overtime work reasonably and follow up the progress of the project every day
2. Time control for each test phase
Testing process, will be divided into a lot of stages, to advance it to set a good time node, and then to control it, so that the test cycle is really within the test time node
3. Control the proportion of time for study, work, rest and entertainment
Working time in the reasonable division of these time, the work must stand at more than 50%, if the working time accounted for 8 hours a day below 50%, then is a unqualified test engineer, leave except not far, in the right time to steal a lazy is ok.
If a person has a poor sense of time, this will be evident at work. For example, I am often late for work. For example, I cannot finish the tasks assigned by my leader on time.
3. Learn to communicate effectively
1. Presentation skills
Presentation skills are very important in communication with developers and in interviews. If a person’s presentation skills are not good, he or she will not be a leader and the room for advancement will be limited. Of course, not speaking, does not mean poor expression ability
2. Comprehension
One is to listen carefully to others, such as the product manager speaking requirements document, to accurately understand his meaning; Don’t interrupt someone when they’re talking. It’s hard to pick up a thread. A lot of people get pushed aside in the workplace and don’t know why. It’s all about the details.
3. Ability to think
Mainly refers to the ability to put forward constructive suggestions. Of course, this need to pay attention to must not always in order to highlight their own and go maverick naysayers, so will die soon.
The other is to listen to others carefully, and finally summarize and extend new ideas, which is the potential of a leader.
Remember not to pretend you know what you don’t
4. Decision-making ability
Decision-making ability is to come up with effective evidence and reasons to persuade the other party.
Others have put forward a set of plans, can come up with effective reasons and basis, tell him that you are wrong, why is wrong, can put the reasons and basis to say very detailed, and indeed the final conclusion is really wrong. In this case, the leader will think highly of you, why not give you a raise.
Effective communication can help you better understand other people’s thoughts and intentions, and put forward different views and opinions. At the same time, it can also make others accept your ideas and plans, so that you can be better accepted by the leaders and more recognized by you
Fourth, improve work efficiency
1. Able to quickly master business
It’s mostly about logic and business processes, not much more
2. Improve the writing speed and effectiveness of test cases
It takes someone two days to write a test case, but IT takes me half a day. I could have fired him and given me a raise.
3. Can quickly enter the test state
When many people just took over the task, they could not enter the state of testing for a long time. Only the more problems they found, the more mechanized mode was formed, and they entered the state. That’s why a lot of people hate to be interrupted when they’re testing.
4. Able to follow up effectively
First of all, it is not effective for many testers to follow up with developers to fix bugs, because they will only urge them in the group.
First of all, we should ask what is the reason for the development of this problem, why there will be such a serious error, how many modules need to change this problem, how much code need to move, this problem to ask clearly, how long it takes you know.
Many testers see problems on the surface, but in reality there are many pages involved, and the more urgent the development, the more nervous they become
5. Able to quickly determine the location of problems
Defect reports must be straightforward, concise, clear, and easy to understand.
What is the problem location? When you find a defect in the page, you can quickly know what caused the problem. Don’t look at the code, that’s a white box test. Also know what actions can be taken to reproduce the problem and be able to write it in Zen or at least clearly.
Only when the efficiency of work is improved, can we do more and more things every day, so that we can be more and more valuable. Don’t feel like you’re being super productive right now.
Learn to put yourself in others’ shoes
1. Be able to think from a development perspective
First of all, don’t shout about a serious bug and make everyone in the company think you’re awesome. This will deeply hurt the developers because they wrote the code.
Second, do not urge developers very hard, because developers are very upset about the bug, but also face the pressure of leadership, and also face your pressure
2. Be able to think from a product perspective
Some disputes on the requirements document or business, not the subjective only consider our test point of view, I think this function is not reasonable, I think this module is redundant, I think the flow logic, I don’t think this is the right coupon is designed, so when you really don’t think this is the right thing, I want you to talk to him if you can talk to him rationally
3. Be able to think from the perspective of the user
Speaking of the user’s point of view, that is, the user experience, every test out of the project, must stand in the user’s point of view to feel whether the project is good, can meet my needs, ease of use is standing in the user’s point of view, you will find more problems
4. Being able to think like a leader
When you will be able to stand in the perspective of leadership, I think you have not far from the leadership, because generally the company’s employees, they only consider is how they can, what I can do, then I can bring what for the company, but there are some employees who is thinking about what I can help leaders to solve the problem, I can do to help leaders to share how much pressure.
When you think you’re all about yourself, you’re never going to see things from someone else’s point of view. You will only backfire and be criticized or criticized by others. When you learn to stand in each other’s perspective to think about this matter, you will feel that there are many things you should not say, there are many things you should not do, so that your way of life, including the atmosphere of your company is getting better and better
Six, improve the level of thinking
1. Think higher and higher
Only when the starting point is high, will the problem be comprehensive
2. Be more and more rigorous about what you do
Some performance in the process of testing, including some performance to follow up defects, including some attitude when doing performance testing, automatic testing, including some detailed reports, these things can reflect your work is not rigorous. Reports written by rigorous people are very perfect. People who are not rigorous, their reports are full of holes.
3. The thinking of judging logic must become clearer and clearer
A function can be considered 10 possibilities by others, but you can only consider 5 possibilities by yourself. This is why others earn more than you because of poor thinking.
For example: business is punctuated with an integral function, can use small white thought is integral, the integral is how come of, how can I get to the integral, how many can use, have reached one thousand points to use goods, integral to change goods can change what goods, this is a small white to see some demand. But a senior test, his judgment logic judgment ability thinking is very high, very active, then he will think about the integral, can be used together with the coupon is correct, AFTER I use the integral, if the refund is returned, then it is not these problems, generally xiao Bai can not figure out.
4. Ability to solve problems to achieve goals
Do not have the idea that there is a supervisor, there is a manager to solve the problem, do not always want to push these problems to others.
Think the problem that others have not thought of, do what others are unwilling to do, solve the problem that others cannot solve
7. Improve the full stack technology
Not to mention the technical, what is missing what. To learn more about testing, solve testing problems, and get started with a guide to help you solve the puzzles encountered in testing, we have technical experts here. If you are looking for a job or just come out of school, or have already worked but often feel a lot of difficult, think their test aspects of learning is not enough to continue to learn, want to change careers afraid of learning will not, you can join my QQ group advanced test learning family: 313782132
Eight, participate in technical training
Constantly improve the scope of their knowledge
Keep learning the latest technology tools
Constantly explore the most advanced testing ideas
Grasp the core of technology quickly, quickly achieve the ability of actual combat
Save as much time as possible to learn, pursue quick results, and continue to improve
Embody your own value
Try to find problems in the test that others can’t
Try to solve puzzles that no one else can solve
Try to take on tasks that others are unwilling to take on
Try to finish a job that others are failing
Do the best of what you can do well, and do the best of what you can do
Ten, good at thinking about problems
Think about work issues
Think about technology
Think about communication
Think about the problem of human life
Think about your problems in the eyes of others
Think about how to do it better, how to solve known problems
According to this way to find their own problems, I believe that we can break through their own bottlenecks. Cut the crap, mind map!
The mind map above has been sorted out by me for some time. If you want to learn from it, you can contact me for communication. In addition, I have also sorted out a part of the network disk materials, which can be directly asked for by me. Code words are not easy, mind mapping is not easy, please give a thumbs up before you go! Much appreciated!