After entering the software testing industry for a few years, many people may enter a bottleneck period and do not know how to improve themselves, but it is a good thing that they can realize this problem.
I also encountered this problem in the past few years. It is really difficult to get out of the comfort zone, but if you can get out, you will achieve your ultimate goal.
Today we will talk about how to improve yourself in the workplace after entering the industry.
The first point: keep asking the bottom line
1. Know how to solve the problem when it is solved. For example, if a bug occurs, you need to know what type of bug it is and what type of problem caused it.
2. For unclear requirements, you should ask clearly before testing, instead of doing it blindly and recklessly.
3. For bugs with a relatively high severity level, it is necessary to track the progress of the modification every day, what is the modification, and how long it will take.
4. Give absolute attention to problems that are difficult to reproduce. You can’t just give up because a problem cannot be reproduced. Solving this problem can directly lead to a great improvement in project quality.
If a test has an "almost" attitude, the first leader will not be at ease, and the second project quality will definitely not be high.
Such a person has no hope of promotion and salary increase, and at the same time, there is no way to improve himself.
The second point: Reasonable control of time
1. Time of project cycle
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 of each test phase
During the testing process, it will be divided into many stages. It is necessary to set a time node for it in advance, and then control it so that the test cycle is indeed within the test time node.
If a person's time concept is very poor, it will be very obvious at work. For example, I am often late for work, or the tasks assigned by the leaders cannot be completed on time.
The third point: learn to communicate effectively
1. Expressive ability
Expressive ability is very important in the process of communicating with developers and in interviews. If a person's expressive ability is not good, then such a person will not be able to be a leader, and his upward space will be very limited.
2. Comprehension
One is to listen carefully to what others mean. For example, when a product manager talks about a requirements document, he must understand exactly what he means;
3. Thinking ability
It mainly refers to being able to put forward constructive opinions and suggestions, and to listen carefully to other people's speeches, summarizing and extending new viewpoints, so that you have the potential to be a leader.
4. Decision-making ability
When someone else has proposed a plan, you can come up with effective reasons and evidence, tell him that you are wrong and why you are wrong, and you can explain it in detail with reasons.
Effective communication can help you understand other people's thoughts and intentions well, and put forward different viewpoints and opinions. At the same time, it can also make others accept your viewpoints and plans, so that you can be better accepted at the same time, and leaders can be more confident. recognize you.
Fourth point: improve work efficiency
1. When many people first took over the task, they could not enter the state of testing for a long time. Only when the more problems were found in the more testing, they formed a mechanized mode and entered the state. This is why many people hate being interrupted by others when testing.
2. First of all, it is not effective for many testers to follow up with developers to fix bugs, because they will only blindly urge them in the group.
First of all, we must ask what is the reason for the development of this problem, why such a serious error occurs, how many modules and codes need to be moved to modify this problem, ask this question clearly, and you will know how long it will take.
3. To quickly judge and write an intuitive defect report, it must be simple, clear and easy to understand.
What is the location of the problem? When you find a defect in the page, you can quickly know what caused the problem. Don't look at the code, that belongs to white box testing.
At the same time, you must know what kind of operation can reproduce this problem, and be able to use Zen Tao or at least be able to write it clearly.
Only when the efficiency of work is improved, more and more things can be done every day, so that it can become more and more valuable.
Fifth point: Learn to empathize
1. Able to think from the perspective of development
First, don't yell when you find a serious bug, and make everyone in the company think you are amazing. This will deeply hurt the developers, because the code is written by them.
Second, don't urge the developers very forcefully, because it is very distressing for developers to fix bugs. Not only do they have to face the pressure of the leadership, but they also have to face the pressure from you.
2. Be able to think about problems from the perspective of products
When there are some disputes about requirements documents or business, we should not only consider the perspective of testing subjectively.
"I think this function is unreasonable, I think this module is redundant, and I think this flow logic is illogical." When you really think this thing is wrong, what you should do is to be able to discuss with each other rationally.
3. Able to think from the perspective of users
The so-called user's point of view is the user experience.
For each tested project, you must feel from the perspective of the user whether the project is easy to use and whether it can meet my needs. The ease of use is from the perspective of the user, and you will find more problems.
4. Able to think from the perspective of a leader
When you can think from the perspective of leadership, I think you are not far from leadership.
Because employees in general companies only think about what they can do, what I can do, and what I can bring to the company, but some employees think about what problems I can help leaders solve. How much pressure to help leaders share.
When you learn to think about this matter from the perspective of the other party, you will know what to say and what to do. In this way, your behavior and even the atmosphere of your entire company will become better and better.
The above points are my personal experience sharing, I hope it can help each of you.
Let me share my guide to learning software testing at that time, hoping to help you who are confused!
1. Pre-basic knowledge:
Computer Basics
test theory
HTML basics
CSS basics
JavaScript basics
Two, linux and database
linux
Database introduction
SQL language (emphasis)
Advanced Database Features
Three, test basis
Software Testing Theory
software life cycle
Test Methods and Classifications
test case design
defect management
Web project combat
test management tool
Fourth, programming + data structure
Python basics
object oriented
exception handling
Modules and Packages
Five, WEB automation
Getting Started with WEB Automation
Basics of WEB Automation
WEB Automation Intermediate
WEB Automation Advanced
Project combat
6. Mobile Automation
Basics of Mobile Automation
Mobile Automation Intermediate
Mobile Automation Advanced
Seven, interface test
Interface Basics
Postman implements interface testing
database operation
Code implementation interface testing
continuous integration
Interface Test Extension
Eight, performance testing
Basics of performance testing
performance testing tools
Project - Interface Performance Test
Project - web performance test
Performance Test Tuning
Nine, comprehensive project combat
Functional testing, ui automation testing, interface testing, performance testing
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:
These materials should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can help you too!