How test engineers "attack the city" (Part I)

What are the basic skills of test engineers ？

As a test engineer , We must first learn and understand the basic skills of test engineers , I believe that many friends who enter the pit either sign up for classes and learn a set of software testing skills , Either by myself or with the help of someone, I learned a series of software testing skills , Most of the skills learned include the following ：

1. Software testing theory
2. Software testing environment construction
3. Linux System usage commands
4. Mysql Database common statements
5. Version or Bug The use of management tools
6. UI/APP How automation works
7. How to test interfaces
8. Use of bag grabbing tools , Learning by agreement
9. Will record some scripts for some performance tests
10. I will also learn some ADB Command some app End of the test

In fact, the content learned above is really quite technical , It's also quite complicated , Especially in a limited time （ Generally, it will not exceed four months ）.

Let's take an example Mysql Database bar , It's really necessary to understand and learn the technology of database , In fact, he can go to work DBA The post of , There are independent training courses for this position .

Let's talk about automated testing , In fact, behind it is the learning of the corresponding development language , There are also special training courses for automated test engineers in the market , There are no more examples here .

So the conclusion is ： It is very challenging for test engineers to learn the above ten items and master them in four months while finding a job .

Some time ago , I've been interviewing , Whether it's a telephone interview or face to face Interview , Among the ten, it is difficult to find one or two suitable for my recruitment requirements , Some people will say that your requirements are too high , Actually, it's ok , It is mainly because the work content determines what kind of test engineers need to be recruited , I pay more attention to ：

1. Previous business logic capabilities
2. Test whether the basic skills are reliable
3. Whether the use of database is mastered
4. frequently-used Linux Will the order
5. It is better to be able to do interface testing

First

Let's talk about business logic capabilities , As a test engineer, if you don't have a strong understanding of business , Then it's hard for him to go far , Because the development of the company is driven by business development , If the test engineer cannot fully understand and master the business logic , Then think about it QA What is the meaning of this role ？

Some people will say that quality is not tested , Quality is designed . That's true , I once said , Instead of saying that , You might as well continue the test （ This is the current situation of the software testing industry , You can't change that ）.

secondly

Is to test basic skills , What I want to focus on here is the design idea of use cases , The design of test cases is the most basic skill of test engineers , If you are going to work in the software testing industry , Then I suggest you design the test cases more thoroughly .

Use case design determines how much you consider business scenarios , The business scenario determines whether the test is sufficient . So what use case design methods should we test engineers master , Such as ： Equivalence class , The boundary value , Cause and effect diagram , Orthogonal experiment , Scene method , Empirical method, etc .

The mastery here is not to understand its meaning , such as ： You know how to use cause and effect diagram ？ Experience method is not necessary for those who are just getting started , No practical experience , This needs continuous accumulation .

In fact, the scene method is what I want to focus on , Because it combines business logic , The use cases designed after considering the business scenarios cannot be replaced by other methods , We should pay attention to .

then

Database skills , The database is the place where the data is carried , It is also the place where data is landing . When we test, we can't just be dots on the page .

You also need to integrate business logic , The business presentation is combined with the data stored in the database to test , The test of data in the database will help us to test some business scenarios, and it is very convenient .

Paying attention to the storage and flow of database data will also find problems that we can't find in the upper layer testing process , Increase the test of the database and put forward the difficult to find pages bug It will make development engineers look at it differently .

And then

Namely Linux Common commands , Why should I mention this , Because at present, all the services we contact are basically deployed Linux Under the system , Then the deployment of the test environment and the tracking and positioning of problems need our test engineers to master Linux Under the command used .

Don't tell me you will cd,pwd,mkdir,tail,grep, ps,top,ls,rm,find Wait for the order to write skilled use on your resume Linux The system , In fact, this is not enough , There are many parameter combination scenarios for the parameters behind a single command .

such as ：tail -f100 a.log |grep -A/-B/-C5 What is the meaning of these different parameters , You have to understand . Go deeper , such as ： stay Linux Build a Nginx service , How to install , How to configure , How to start , How to monitor whether it works properly , How does it work ？ This is a great test for test engineers . You may say that this is not the job of an O & M engineer ？ I tell you , You are wrong to think like this .

Last

It is the mastery of interface testing technology , The test engineer can master the test principle of the interface , Understand what interfaces do , This is very helpful for later interface automation , Don't start the work of interface automation testing at first , You have to understand the interface first , What does it look like , How is it called to process the return .

Also, interface testing is generally the pre work of function testing , So the interface test is also a useful example to design , Use case design should be combined with interface documents , database , Business scenarios , How to locate the problem when interface processing fails .

You can't throw problems to development engineers as soon as you find them , Be able to find problems , At the same time, it is also combined with relevant information （ journal ,F12 debug, database , Configuration information , Service call chain, etc ） Position the problem , This is provided to development engineers bug They will take the initiative to help you solve , Maybe in this process, you will find some problems that you can solve without asking the development engineer .

Such as ： The structure of the service error report is incorrect , There is no call log when the service dies , The service configuration is incorrect ,Nginx Incorrect configuration, etc .

Due to the limited time and energy of test engineers , Everyone should pay attention to the primary and secondary , Don't think about eating all the ten items mentioned above at one time , The above five points are what I think we should focus on , Other skills should be understood and valued , Because it will be the chip for your next gorgeous turn .

In the follow-up work, you have a lot of time to study deeply , Constant practice , There is no project practice to find opportunities to join the project , The project is not suitable. You can build your own environment and practice by yourself , Only through practice can there be true cognition .

summary

Today, I mainly shared some experience about new test engineer , Test engineers need to keep learning , Always on the way of learning , Keep learning every day , Keep typing . Education represents the past , Ability represents the present , Learning power represents the future .

Friendship tips ：“ The way of immeasurable testing ” Original works , Welcome to exchange , It is forbidden for a third party to reprint the article without displaying its source .