Testing the basic capabilities of Internet advanced test engineers

Familiar with the system

The various business scenarios for testers participating in the test system must be mastery. Once the requirements have changed, you can clearly and quickly know the context. At the same time you can clearly know which points are needed to focus on testing. Be familiar with the upstream and downstream system business with communication with the system

The upstream and downstream systems that have communication with this system should also be very familiar. So once the system is in trouble, you can know the extent of the impact. Click to open the link
Familiar with company main process business

Familiar with company main process business. Although not your own test system, but familiar with the company's main process business, you can allow testers to consider the issue, there is a better and broader thinking.

It's better to be logical.

Internet applications are generally divided into subsystems, each system has its own business scope, the completion of a task, usually have a number of departments or groups to collaborate. At this time, it is unavoidable to carry out various meetings of communication, within the group or between groups. Then the tester if the brain is not good, can not quickly understand other people's intentions and ideas, will be easily fooled or caught in various pits, then there will be endless testing tasks. In addition, when the other side is too strong, the tester can not be too weak, should be based on their own business and system understanding, put forward their own opinions, should do, do not do not hard to plug over. Actively cooperate with each other, but not silly to do anything.

Control the system online scheduling

If the development task is very much, testers will have to test a lot of functionality. At this time, if the function of the on-line time is the development manager or PMO, and so on, the tester can only do endless overtime. This is not going to work. Testers have their own professional, to the business mastery, must clearly know which task priority is high, which is low, prioritize tasks. Specify how many functions you can have in a certain time period. The maximum number of task queues that the test team can withstand, and testers must have a bottom. The test task exceeds this queue, and you can squeeze part of the task out of the priority level.

Ability to write test cases that cover critical paths

Accurate understanding of business needs, testers can be based on business needs, design key test cases, can complete coverage of business critical paths and scenarios, to ensure that as long as these key use cases can be passed, it shows that the focus of the requirements of the function has been OK. Key function OK, even if immediately online, if there is a problem, but also a small problem. Of course it is best to cover all of them with test cases.

Familiar with Test technology

When testing Internet applications, the test should at least have the following techniques and concepts:
1. Know how to use jmeter for performance testing;
2. Know how to build the environment for performance testing, such as server, Redis, memcache, etc.
3. Know how to write performance test reports. Examples include at least interface response time, QPS, best concurrency, CPU usage, memory, jitter, GC, and so on.
4. Understand the concepts of context switching, memory overflow, memory leak, QPS, stability testing, etc.
5. Uat is an extremely important step in understanding how to do online uat validation, especially in projects that require multiple systems cooperation.

Constraining developers to ensure development quality

When developing a test code, testers should have the following consciousness: 1. Let the developer first merge or rebase the code of the Master branch into its own branch, ensuring that the code already contains master code when the test is made, so that the problem can be identified in advance.
2. After the completion of the Code function test, you must do a regression test again. This is a time when developers must be strongly constrained and no longer allowed to submit code. Unless it's a bug. Otherwise, after the tester returns to the test, the developer runs to tell the test that the code has changed. In this way, the tester's hard-earned regression test was measured, and it had to be returned again.
3. The tester must reclaim the code submission permissions of the Master branch, and once the developer submits the code, it can only communicate with the test and explain what changes the code has made. It is absolutely impossible for developers to silently submit code, which is a very good way of causing online failures.

To understand the write code for interface Automation test

Now the micro-service is very popular, the major Internet companies are engaged in micro-service interface. For the micro-service interface, testers must know how to write code to perform interface Automation testing. Think about it, assuming that a system has 50 micro-service interfaces, testers after testing, the developer modified the 10 interface code, this time should be able to run automated case to verify that the 10 interface changes have affected the other 40 interfaces. The efficiency of this regression test is very high. If you have to manually perform an interface regression test each time, the tester will be exhausted.

--------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------- ---------------------------------------------------------