A large factory developed and tested one, and strangled its neck with a mouse line

Develop and write code , Test to find out bug, A disagreement can lead to red eye disputes from time to time . One netizen revealed his company , It is said that a department has started testing and development , It was very noisy , I heard that I also strangled my neck with a mouse thread ！

Onlookers said ： How can the wireless mouse break ？

A joke is a joke , But if software testers really spend a lot of time fighting with developers , It's not always worth it . Let me show you which minefields can be avoided , Blow it up as soon as you touch it ~

01、 Test submission Bug Description missing screenshot

“ Every time bug, Development makes data clear 、 Clear cache 、 Restart the machine , Three or two times bug It's all gone , wait until bug Can't reappear , Let's see , Can't emersion , It's not fixed ！”

As a tester , Have you ever had this experience ？

So submit next time Bug When describing , Remember to add screenshots of auxiliary pages , On the one hand, the expression is clearer ; On the other hand , Some accidents bug leave “ The scene of the accident ” The evidence of , I can't help but believe him , Of course , If there is a short video recording screen better .

02、 The unprofessional tester leads to unclear description

If it's not the test of technical background , Will be refuted by developers who don't understand the code ; You can't use technical terms to describe bug And the correct result description is clear and in place , It will also increase communication costs , The result is bad . Or front end 、 Back end 、 The design problem is Bug Not distinguished in , Need for Bug Make the right priority .

Want to make the development unable to find faults , Testers should improve their technical ability , No matter the function is realized , Or code logic , All need to be clear in your heart .

Be familiar with at least one language , Whether it's Java,Python still Go, Master it 1-2 Just one . With the foundation of language , Testing can provide a deeper understanding of product implementation , Can also know more clearly bug Modules that often appear , Be able to test the product more fully .

03、 The test did not intervene as early as possible , There are too many changes to the requirements of updating in the later stage

When to intervene in the test ？ The sooner the better .

In the whole process of software development , Demand analysis 、 Design 、 code 、 test 、 Release maintenance , It is possible to introduce software defects , The cost of fixing software defects increases over time , Test and find software defects as early as possible , The less manpower and material resources are invested in the correction .

Sometimes the test will find that the original product has logical omissions or errors 、 I feel that there is a better way to realize some functions .

When this happens , Don't rush to make new demands , But to communicate with programmers first 、 Listen to advice , How can consultation achieve its goal with the least change （ Note that it is not necessarily the result ）.

If you really need to raise new demands （ This is one of the most developed places ）, Pay attention to the way when communicating with developers , It is best to incorporate the requirements pool and complete it in the next version iteration , The way to deal with this is whether you are good or not . If new requirements are always raised during testing , Not to mention the psychological shadow area of programmers , The pace of product development will also be completely disrupted .

04、 The two ways of thinking are different

Develop features that focus on programs , And work under the guidance of existing requirements and design , They often don't think from the perspective of business logic and users . After finishing the work , They will stubbornly believe that the code they write will work well . And testers usually find problems from the perspective of users , Through various test cases, the potential shortcomings of the software are exposed , This is the difference between the two ways of thinking .

As a test , In addition to adhering to the perspective and position of your own test , Have empathy, too , Learn to look at problems from the perspective of development .

Many conflicts stem from different understanding of requirements , When testing and developing for a bug When you have different opinions , Don't take the lead in denying him , Try to explain why the needs he understands are inadequate . Find some tenable arguments , From the user's point of view , From a security point of view , Or in terms of ease of use and friendliness , Persuading developers to accept the idea of testing , Instead of imposing their own opinions on them .

Test engineers should improve their EQ , Improve your communication skills , Know how to think from the perspective of development , Learn to respect developers .

05、 Other development reasons

Other aspects include ：

Workflow ： Don't have the time , The problem is too small （ Low priority ）, The online time is urgent , Not under my own name bug（ Left by retired developers bug）.
Develop personal ability reasons ： No solution found , Technology is hard to achieve . Some developers are only good at code function testing and code repair , If the program works properly , Then their test is over . And the test needs to disassemble the application , Look for those hard to find in each small piece bug, And help developers understand what those specific functions should be like .
Objective factors of force majeure ： For example, system problems , The third party SDK Questions, etc .

The way to solve these problems is , Establish a sound management process , Standardize the work of development and test department through process control , It can greatly reduce the occurrence of conflicts .

Last , Quality assurance is not just the responsibility of testers , It requires the whole team to work together , I hope development and testing can understand each other , Help each other ~

Learning resource sharing

Finally, thank everyone who reads my article carefully , Watching the rise and attention of fans all the way , Reciprocity is always necessary , Although it's not very valuable , If you can use it, you can take it

These materials , For those who want to learn by themselves 【 software test 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ Everything should be done as soon as possible , Especially in the technology industry , We must improve our technical skills . I hope that's helpful , Join my communication group below for free ！