What are the strengths of "testers"?

First , Excellent software testers need to have the following conditions （ essential ）, If you haven't mastered these basic skills , You must work hard on your basic skills .

1. Software testing knowledge ： test plan 、 Test plan 、 Write use cases 、 Submit bug、 track bug, Write test report

2. Use of test tools

3. operating system

4. The ability to write code

5. Database knowledge

6. professional knowledge 、 Network knowledge

secondly , After mastering the necessary skills ,“ Test Daniel ” What other qualities are needed ？

01 Take the initiative to communicate

We can completely test according to the requirements document , as long as bug The description is clear , Development approval , It's not a big problem if you don't communicate in the ideal state . Except that we don't understand the needs , The development is inconsistent with the requirements we understand , Then we need to communicate with the product manager .

But in the field of e-commerce , It is characterized by speed and change . Some requirements or projects , It is often required to go online quickly , Must be completed within a certain time , And it may change in the middle and late stage of the project or at any time . in addition , Time is short , The requirements may not be so detailed , So perfect .

Let's face it , What should I do about the test ？

It's communication , communicate , Communicate again . Communicate needs with products at any time , Communicate design with developers at any time , Communicate the test environment with other systems at any time , Test data .

Testing in the field of e-commerce , No communication , Can't do anything . communicate , You have to take the initiative , If you are passively communicated by others , The project is expected to fail .

02 Calibrated boldness ： Believe that you are professional

The tester has one characteristic , Before going online, I always worry about whether there is something I haven't detected , Will there be any problems when going online ？ Especially when encountering major projects , Even more so .

I suggest you do this ：

After the test is completed , Calm down , Think about the overall process of the project , Then analyze the core functions of the project ;

Communicate with developers and products about their test points , See if there are any omissions ;

Finally, suppose , What kind of problems may occur after going online , If there is a problem with an important function , Do we have any countermeasures ？ without , Then make a plan as soon as possible .

03 Have a skeptical attitude towards everything

Better believe than have no book . Completely believe in requirements and design documents , Like no test , The value of the test will be greatly reduced ！

For the test , Is to doubt everything , Doubt every detail of every process , Of course, it should be based on understanding .

When looking at the requirements, it is basically assumed that he is right for the first time , When you have a certain understanding of the whole , I began to doubt ：

Whether the process is complete , Is there a loophole , Whether the module function can meet the requirements of users ？

Whether abnormal operation will cause problems ？

Which systems will use the generated data , Whether it can be used ？

Is there a lack of data ？ Whether it will cause redundancy ？

Whether users feel easy to use this function , Will you feel troublesome ？

Does this function really solve the problem for customers ？

All in all , Test every function " Think twice before ".

04 Consider the problem from the perspective of the company and users

The bigger the company , More departments , The more complex the system will be , Interdependence . Nowadays, few systems are completed independently .

So as a tester , The final gatekeeper of software quality , You can't just see the part you're responsible for , You can't limit yourself to your own department 、 The team , As long as problems are found , Whether it's your own , It's from other systems , There is still no clear person responsible , We all have the responsibility to bring it up , Find someone to solve it .