Basic Skill Requirements of testers-quick grasp of business knowledge

Note: This article is excerpted from Chapter 3rd of software testing technology Daquan

The skill requirements of testers are less specific than those of developers. developers can be competent for development simply by requiring the ability to use a certain programming language. However, testers need to know more and learn a wider range.

Therefore, the skill requirements of testers can be summarized as the ability to quickly learn new things. Because the testing project contains all aspects of the content, different projects use different technologies, and involve different business fields, the testing methods and testing tools that need to be used may be different. There is no project that gives testers plenty of time to learn.

 

TIPS: You must be able to learn quickly, grasp the key points, and be good at analyzing and using useful information for your own tests.

 

The skills that testers need to master can be divided into the following four categories:

Q project involves the ability to analyze and understand domain knowledge.

Q: analysis and understanding of product design and architecture.

Q. application capabilities of various testing methods and testing tools.

Q: ability to analyze and understand user models.

 

The four aspects constitute the "skill matrix" of excellent testers, as shown in Figure 3.5.

Figure 3.5 skill requirements of testers

As you can see, testing knowledge is only part of it, and the core skill is the ability to learn quickly.

 

3.2.1 business knowledgeThe more you know about the business, the closer the test is to your actual needs. The defects found during the test are also very important to users. They are also important to project managers and developers. This is especially true in some business application systems. On the contrary, if there is a lack of understanding of the business areas involved in the product, it is possible that the tested defects will only stay at the functional operation correctness level and will be considered incomplete by developers; even worse, due to misunderstanding of some business knowledge, it may lead to a false test, and the submitted bug is angrily rejected by developers. TIPS: Read more demand documents, consider issues from the user's perspective, and communicate with users or demand analysts. This is a good way to discover more business defects.