"Turn" test thinking-what qualities should testers have?

Previously written articles, shared today

What qualities do testers need?

What skills do testers need to have?

1. Software Testing Knowledge: Test plans, test scenarios, write use cases, submit bugs, track bugs, write test reports
2. Use of test tools
3. Operating system
4. The ability to write code
5. Database knowledge
6. Business knowledge, network knowledge.

Besides these necessary skills, what qualities do we need?

First, active communication
I used to do traditional ERP software testing, because the ERP software is very mature, so his requirements are generally very well-documented, very detailed, not too much change in demand. So we can completely follow the requirements of the document testing, communication with the development of the telephone is OK, as long as we have a clear description of the bug, development recognition, the ideal state does not communicate the problem is not big. In addition to our understanding of the need, development and our understanding of the needs of inconsistent, then we need to communicate with the product manager.

But in the field of e-commerce, the characteristics are rapid and change. That is, there are requirements or projects that are frequently required to be launched quickly, must be completed within a certain period of time, and may change at any later stage of the project or at any time. In addition, the time is short, the demand may be not so detailed, so perfect. In the face of such a situation, we test what to do? No way, is to communicate, communicate, and then communicate. Communicate with the product at any time, communicate with the development of the design, and other systems at any time to communicate the test environment, test data.

E-commerce field of testing, no communication, difficult. Communication, but also must be proactive, if it is passive communication, the project is expected to be defeated

Second, bold but cautious; believe in yourself, you are professional

Testers have a feature, on-line before the total worry about whether there is no place to test, online will not appear problems? This is especially true for major projects. As a professional tester, I feel that I should have confidence in myself, believe in myself, believe in my professional level, and of course, self-confidence is based on the confidence in your own professional and experience.

But what if you're worried? I usually do this: after the test is complete, calm down, think about the overall process of the project, then analyze the core functions of the project, and then communicate with the development and products of their own test points to see if there are omissions. At the end of the assumption, what kind of problems may arise after the launch, if there is a problem with an important function, do we have a response here? If not, then make one as soon as possible!

Third, not to be kidnapped by others, to have professional standards, but also to have their own attitude

The most basic standard of system testing is the requirement specification; As a tester, we are the last guarantee; We must have our own thoughts, we cannot trust others easily, and follow other ideas, because what he tells you is already processed by their thinking, and may be biased with the original needs.

Of course, what they say is right, it's true, but it can only be a material for us to think about. We must analyze our needs by ourselves, with requirements described as criteria. So the test will not lose our foundation.

Demand is the standard we test, but the standard is also wrong, so at this time we have to ask us to have their own thinking results, have their own attitude. don't give up on your attitude unless it proves that we are wrong.

To have a skeptical attitude towards everything.

It is better to have no book than to believe it, and to fully trust the requirements and design documents, as without testing, the value of the test will be greatly compromised! For testing, it is to doubt everything; every detail of each process; Of course, doubt is based on understanding. When I look at the demand, the first time the basic default he is right, and so on the whole has a certain understanding, I began to doubt that the process is complete, whether there are loopholes, the module function can meet the requirements of users? Whether there is a problem with abnormal operation, and which systems are used for the resulting data? Is it possible to use? Is the data missing? Does it cause redundancy? Does the user feel comfortable with this function, will it feel trouble? Does this feature really solve the problem for the customer? In short, test every function to "think Twice".

Five, the responsibility of the company and the user's perspective to consider the problem

I asked a lot of people in the interview, what qualities should testers have? Everyone mentions the "sense of responsibility".

But what is the sense of responsibility? How to do it? I feel that responsibility is to the software quality to have a responsible attitude, the company has a responsible attitude to the user has a responsible attitude, responsible for their own work, and then intentions to do things.

The larger the company, the greater the need for our sense of responsibility, because this is unable to use the data to judge, only through the phenomenon to analyze. The bigger the company, the more departments will be, the more complex and interdependent the system will be. Now very few systems are done independently. so as a tester, the final gatekeeper of software quality, can not only see themselves responsible for this piece, can not be confined to their own departments, teams, as long as the problem, whether it is their own, is other systems, or no clear person responsible, we have the responsibility to put forward, to find someone to solve. as long as it is a problem, it should be solved. Maybe others laugh at us too silly, "I laugh at others do not wear."

"Turn" test thinking-what qualities should testers have?