Excellent software testers have these abilities

One 、 Software testers should think of danger in safety

As a tester , Although most of our normal work is comfortable . But never cook frogs in warm water . We should keep improving ourselves , Keep on learning , Improve your testing skills . Because the test threshold is a little lower , If you slack off , It could be replaced at any time . The point is to learn more about testing technology , Then apply the technology to existing projects .

PS： Those who want to learn software testing can enter this official account and click ： Contact the author

Two 、 Testers should be more familiar with business requirements than developers

The level of testers is mainly reflected in the design of test cases . To design a comprehensive , Extensive test cases , Testers need to be familiar with the business requirements of the projects they are testing , Even more familiar than developers . If it's testing the banking system , Communication industry , perhaps ERP Software . This business knowledge is very useful , It's more exciting to learn .

It's not easy to be proficient in business requirements .

Read the functional requirements document carefully , Go anywhere in doubt and PM confirm .
Think of yourself as an end user , Always use the software you test . Simulate user behavior .
Memorize every function of the software .

PS： I'm tired of my work , Dry eyes , Xiaobian strongly recommends this steam hot compress eye mask , It's really comfortable after application ！

3、 ... and 、 Learn how to get along with developers

Testers must work closely with developers , So it's very important to have a good relationship with developers .

1. Make friends with developers .

I'm familiar with everything

2. Don't disturb developers . See the time when developers concentrate on writing code , Don't disturb others . Writing code requires concentration , If disturbed , It will stop thinking .

3. Focus on questions . Sum up all the questions that need to be asked , Focus on Development , This can save a lot of time .

4. Write well Bug, Not bothered by developers .

If a developer sees a Bug Unclear description , It can't be reproduced yet , He's bound to scold the testers . So the tester must write it well Bug, Description accuracy , concise , There is no ambiguity , Detailed and concise reproduction steps , Add screenshots .

Four 、 Improve the ability to write documents

There are many places for testers to write documents , Normal test cases 、 test plan 、 Test reports, user manuals and so on all reflect the importance of the ability to document testers , If we go to TestLeader Development , Also very good at summarizing test reports , Be able to complete , Clear , Beautiful test reports to all groups , So that everyone in the company can clearly see the work of the test group .

5、 ... and 、 implement “ One to many ” The pattern of

“ One to many ” The pattern of "the world" refers to ： One person can test multiple projects at the same time , A project is tested by multiple people . Because everyone has different opinions and different ways of operation , So the possibility of finding problems is not the same , It's better to find out what's hard to find bug, A test engineer tested his project for a long time , Easily form blindness . Yes, some. Bug Look at for a long time but not to see anything .

6、 ... and 、 Establish a complete testing process

The testing process is pretty much the same , But there's still very little to do according to the process . If conditions permit , We should try our best to follow the process , Unit test first 、 And then integration testing , Instead of just testing the system .

7、 ... and 、 Testers should learn more

First time test , It may still be in the stage of exploration , It's not clear what test related techniques to learn , At this time, we need to take the initiative to find , Watch what others do through books and online 、 Draw useful lessons from it , Avoid detours . The technology that testers need to improve covers all aspects .

for example ： Performance testing （ Reference tools loadrunner、JMeter,locust）、 automated testing （ Reference tools Pytest、RobotFramework）、 Scripting language （Python）、 database （SQLServer、Oracle、Mysql）、Web automated testing （Selenium）、APP automation (Appium) wait , There's a lot more , So much technology , Learning is just one aspect , More importantly, according to our existing project and test environment , To analyze what is the most suitable , Only in this way can we really apply what we have learned to the project .

today , Let me share with you the knowledge architecture diagram of the development direction of software testing engineers , I hope it can bring you inspiration and direction .

I believe that if you master all the following knowledge and skills , And can be used flexibly , a monthly salary 20k-30K It won't be a problem . It's a process that's going to kill you , But as long as you get through it . Life will be much easier in the future . I've come a long way , To get more high paying jobs , It pays off , It can also be regarded as a recognition of self-ability , Really proved their value .

7.1 Linux You're supposed to know

Linux As the most popular software environment system now , It must be mastered , The current recruitment requirements need to have Linux Ability .

7.2 Shell Script

master shell Script , Include shell Foundation and Application 、shell Logic control 、shell Logic functions, etc .

shell I understand , You can also touch windows Batch processing of

7.3 The principles of the Internet

The only way to automation ： Basic knowledge of front-end development and necessary knowledge of Internet network .

7.4 Mysql database

Software test engineer must Mysql Database knowledge , It's not just about basic “ Additions and deletions ”.

7.5 Caught tools

Fiddler、Wireshark、Sniffer、Tcpdump Various bag capturing tools are suitable for various projects , There's always one for you .

7.6 Interface testing tool

Interface test artifact , Powerful tools you can't get around ：Jmeter. Small and flexible ：Postman.

7.7 Web automated testing Java&Python

Understand the purpose of Automation , Have a good command of testng&unittest Automation framework , And assertion and log processing ,Page Object Design patterns

7.8 Interface automation

Common solutions in the industry ：

Python + requests Use programming to solve
The other is with the help of some interface testing platforms and tools , for example ：jmeter+jenkins,Eolinker,yapi,apifox wait

7.9 Agile testing &TestOps structure

uncover TestOps The veil of mystery , Continuous integration Jenkins The frame is familiar with the heart .

PS： I'm tired of my work , Dry eyes , Xiaobian strongly recommends this steam hot compress eye mask , It's really comfortable after application ！

7.10 Performance testing & Security testing

The other side of software testing ： Performance testing and security testing , Select the right direction , Try to climb the pit ！

The house needs to be built layer by layer , Knowledge needs to be learned at one point one . We should lay a good foundation in the process of learning , More hands-on practice , Don't talk much , The last dry goods here ！ I stayed up late to sort out the stages ( function 、 Interface 、 automation 、 performance 、 Test open ) Skills learning materials + Practical explanation , Very suitable for studying in private , It's much more efficient than self-study , Share with you .

Get off w/x/g/z/h： Software testing tips dao

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .