<> One , What is the nature of testing
I think there is no standard answer to this question , As far as I'm concerned , Testing is to test specific products according to certain standards ( This is software ) Carry out the test , Here are two key points ： Certain standards and tests , Specifically, software testers should not only understand this standard , Also familiar with the detection method . To go a step further , As a tester , What is beyond this standard and how to solve the detected problems are not the focus of our work , If you're trying to do something outside your area of responsibility , That's what troubles you .
<> Two , What is your duty
Generally speaking, software testing is testing , Write test cases , Perform tests , Writing defect reports and other miscellaneous things , Specific to each organization, each person will be different , And you need to be clear about your responsibilities , This is your job and further development , The premise of improving oneself and creating more value for the company . If you are an ordinary tester , Your daily work is learning needs , Design test cases , Perform tests and report defects , In addition to these duties , You can also do some other meaningful things for the entire test workflow , For example, improve the test case template , Organize new colleagues' learning documents, etc , These are benign and appropriate extensions , It's good for you and the company ;
You might do something like that ： Complain about unclear requirements , Put forward some improvement suggestions that are too subjective and not needed by users , Complain about the poor working quality of developers , Try to change or drive the whole project process unrealistically , Overemphasize one's position, etc , These things are unnecessary , Especially when you're a rookie .（ If communication is needed , Additive penguins ：1039627644 remarks ） It needs to learn to grasp a degree , Of course, you can also try , For example, you can suggest that developers improve their development quality , It can be suggested to leave more time for testing , But don't get tangled up when you realize there's no egg to use , Think about your responsibilities .
<> Three , Responsibility boundary
Some testers , In particular, some new beginners put too much emphasis on responsibility , If something goes wrong, I'll blame myself , Even the problems caused by developers come down to themselves , Make yourself tired , At first glance, it's not bad , Don't companies like people like that ? I'm not saying there's no need for accountability , It's about being appropriate , It's just a job , So what does self abuse do . Of course, in reality, there are many cases of shirking responsibility , That's not good, of course , What I want to say is , We need to make clear the boundary of our sense of responsibility , It's not a sense of responsibility .
<> Four , Measurement of test
Measurement of test , user demand . There are many colleagues , Especially some new colleagues , Often like to impose their preferences on software projects , For example, a font is too large , Some hint is not very friendly, etc , And these “ problem ” The user didn't care , What do you need to worry about , Maybe someone is going to say it , Isn't testing about ensuring software quality ? you 're right , But the quality you need to ensure is based on the user's standards , From a business point of view , It's not necessarily a good idea to give users products that exceed expectations , Here, we need to take into account the specific situation , If it's a product ( Independent R & D and resale ), You can make some reasonable suggestions ,（ If communication is needed , Additive penguins ：1039627644 remarks ） But if it is to develop projects for customers , Then you can think about whether it's necessary to give customers a bunch of friendly suggestions . There are no rules here , Not even good or bad , It's just that we don't have to worry about it a lot of times , You need to have that energy, even to watch the news .
<> Five , Get rid of the problem
After defining the measurement standards of their responsibilities and work contents , Let's talk about it , Ask if the need is not clear , Write test cases carefully , Get the software and test it , Find defects and seriously raise them , Write the document well , It's not easy to do that , Where else do you have to deal with the development , Where do you blame the good or bad demand . We should learn to throw out problems that are beyond our responsibilities and that we are uncertain about , For example, developers say it's not a problem , You think it's a problem , You don't have to argue , Take the demand and the project's superior leader to talk , What to do , We are only responsible for asking questions that do not meet the requirements , And don't stay at home if the needs are right .