I think the most important thing for software testers is to have certain theoretical knowledge and testing skills, which is the basis of testing. So what other qualities should our testers possess in order to be continuously recognized at work?
A good tester should have the following qualities:
I. Be steadfast, careful, and proactive
I think that as a tester, we must be steadfast and careful. Careful: you don't need to explain it more. The careless person cannot do a good job of software testing. Software testing, especially the mainstream manual black box functional testing in China. Basically, software testing is a repetitive task and requires patience to ensure that small defects are not put off in tedious repetitive work. Testers face boring programs every day, engage in a lot of repetitive work, and try to find bugs in products. If you are not steadfast, you will not be able to sit still and want to do anything else. You will not be able to think about how users may use the service and what requirements the product has, how is the current product made? Where can there be problems. Not careful, it is especially easy to smile in some products, but these errors are the most influential problems.
As for the initiative, I will not talk much about it. This is what everyone should have
Curiosity, doubt everything
Testers can't find any problems if they just run the project on hand. The main purpose of our testers is to discover software defects, rather than prove that the software has no defects. If you do not doubt everything, you are not a qualified tester. Products tested by your hand face direct users. You are not responsible or skeptical about everything. I always thought that this feature version should be free of action. I think most people will not perform this operation. This feature is useless for users and does not need to be carefully tested. I am afraid to use the product. It is strange that users use products. Some users have a deeper understanding of products than ours. Therefore, we must be skeptical about everything. From multiple aspects, we think that every function of the product may have a problem. Ask another "why" and "if so, will this work ?」, Carefully test each test point of the product.
3. Good communication skills with others
As we all know, the test process is a process of discovering and tracking and solving problems. In this process, we must realize that testing, development, and needs are a team and a whole. The quality of the product cannot be guaranteed. As a particularly important soft skill, communication skills play an important role in the work. As a tester, we need to be clear when submitting a question. If necessary, we need images to help others understand the problem. This is not acceptable only when we can understand the submitted question. We also need to communicate with the project manager to learn about the latest customer requirements and to communicate with developers to solve the defects. I have seen a humorous conversation between developers and testers:
Daily test:
Development: this is not a software issue. I have read the test code. This is a bit of a problem. It shouldn't have been tested like this.
Test: Is it true? Let me see... Really. I will submit it... Thank you for helping us find this bug.
Development: OK, no thanks... (What does it feel wrong)
The attitude is very important when talking with the project manager or the developer. Here, I am not talking with them in a humble manner, especially when talking with developers, there may be a conflict between the two due to a bug. At this time, our testers should analyze the problem and listen to the developers' ideas and communicate calmly, in the end, both of them are not sure. You can ask your superiors for help.
4. Continuous self-improvement and summarization
In my opinion, no matter which industry you are in, you cannot stagnate. Self-improvement is a must and will not be eliminated. How can you improve your testing capabilities as a good tester?
First, improve the theoretical basis of your testing. All basic concepts of testing are actually common: static testing, dynamic testing, test cases, and some test-related technologies: equivalence classification, boundary value, I believe that all of these methods are used every day, but not all of them can be explained. Therefore, finding a theoretical basis for your daily testing activities, that is, combining efficiency with practice is also an important step in career development.
Second, we need to have a complete concept of the overall test process. This is currently lacking by many junior testers. At present, most people only know what they are testing, but do not know what stage they are executing the test, what is the next stage, or maybe the whole project is finished; this is an irresponsible action for a product. Therefore, testers need to have an end-to-end testing consciousness and a recognition of the concept of the testing process. They must have the concept of testing the overall process management.
Third, we need to understand why we should do this, why we should execute such cases, and why we should execute relevant testing work. Ask more why. There is a problem that needs to be clarified first, that is, many people have not noticed this problem, and the leaders may be very skilled in doing what they want, however, if I asked him why he was doing this one year later, I believe he could not say too much. Instead, I thought it should be the case. The direct drawback is that you are not responsible for your career path.
In addition, I think that as a qualified tester, we must make a summary. Through the summary, we can review and analyze our work to see which ones are doing well and continue to do so next time. There is room for improvement in those jobs. It is a good help for improving your own capabilities.
5. Strong sense of responsibility
Many testers come to the office in the morning to complete their tasks and return home from work in the evening. When software testers complete their tasks and pick up their work and go home from work, does this conventional way of working sound normal? Yes, we have to say that we are in this status currently. How can we take responsibility for a high-quality product?
Testers should be responsible for the quality of the tested objects, and ensure that the testing covers every requirement point, at the same time, it is necessary to ensure that all functions can be correctly implemented or meet the testing criteria.
For testing personnel missed tests, after all, people are not perfect, and errors may inevitably occur, but they cannot be used for quality assessment. You can perform classification analysis on the problem arising from the specific link and propose improvements. For example, the requirement description is incomplete, leading to incorrect understanding; the implicit requirement is not taken into account; the usability is not considered weekly; the actual environment is different from the Test environment; and the actual experience is insufficient.
Testing is to prove that the product has done the right thing and can meet the needs of users. Using various testing methods to identify problems is a measure of quality. Good quality is guaranteed by high-quality personnel and good processes.