Finally got byte offer. The 25-year-old inexperienced perception of software testing is written to you who are still confused

Two years of software testing , Over the past two years , From the beginning of the hazy understanding of the test , Now the train of thought is gradually clear , It also makes clear its own development direction . Although the testing theory and testing tools as well as testing technology have been strengthened , But I still don't feel deep enough .

​

I've always wanted to really get into the test queue , Let your understanding and technology of testing go deeper every year , Become a professional Tester . I've sorted out my thoughts these days , This paper reviews some ideas of testing in the past two years . If you don't know how to start learning ？ hinder 《 Software test engineer development planning route 》 and 【 Software testing learning resources 】,【 Interview treasure 】, It should give you help and direction  ​ ​ Have a pleasant surprise ：【 Test Engineer - Test Architect Collection of learning materials 】​​

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 .

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 .

It's no use if we have some bad luck , Cumbersome software , I really don't want to learn its business （ A business that can no longer be used outside this company ）

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 , Maybe it's still in the exploratory stage , It's not clear what test related techniques to learn , At this time, we need to take the initiative to find , Through books and online to see how others are doing , Learn from available experiences , Avoid detours . The technology that testers need to improve covers all aspects .

for example ： Performance testing （ Reference tools loadrunner）、 automated testing （ Reference tools QTP）、 Scripting language （VBScript、Python）、 database （SQLServer、Oracle）、 Operating platform （windows、Linux）、Web test （Selenium） 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 .

This 2022 It may be the most comprehensive development direction of software testing engineers, knowledge architecture diagram , I hope it can bring you inspiration and direction . Click on ​ ​【 Test Engineer - Test Architect Collection of learning materials 】​​​ receive ！!

《 Software test engineer development planning route 》

800 Interview questions for software test

Software testing learning resources

The material includes a lot of common knowledge in the testing industry , It includes basic knowledge 、Linux necessary 、Shell、 The principles of the Internet 、Mysql database 、 Special topic of bag capturing tools 、 Interface testing tool 、 Test advanced -Python Programming 、Web automated testing 、APP automated testing 、 Interface automation testing 、 Testing advanced continuous integration 、 Test architecture development test framework 、 Performance testing 、 Safety test, etc.