A long-lasting voice
The test engineer deserves to be respected. It has always been my inner voice. This voice has been held for a long time, so this article feels that it is not a title party, but a real inner thought. Of course, it may be extreme, it may be too general, or it may be P words, but I believe it will directly resonate in your heart!
If there is something wrong, I hope you can forgive me, we are all civilized people, you know~
It has long been considered low barriers to entry
Painful realization! I want to smoke my mouth too! In the early years, I myself said that the test entry threshold is low or something, now think about it, alas.
First of all, there is no denying that the threshold for entry to the test is low. This low actually means that everyone has the opportunity to do the test, but most people understand it wrong. Just like everyone is a product manager, anyone can do it , but some people haven't done it systematically, but they don't feel it, but they already have some of the characteristics of a product manager! The same is true for test engineers, and so are development engineers!
Therefore, you can't think about how the test is and how it is without content just because of the low threshold. To be honest, all industries have the same low barriers to entry! The final comparison is who can take root here and who can persist in long-term development. Sometimes we complain because we are not persistent enough!
The inherent thought test has no technical content
In other words, many people think that testing is just a little bit, without technical content! Let me go, big brothers and sisters, don't you think so! I will list a few points for you:
1. I think doing testing is also very tiring. You have learned a lot, and you are obviously a test engineer. Well, if you develop weaknesses in knowledge, you will be ridiculed! So it’s okay if the development engineer’s testing knowledge is weak? For Mao, we are always being criticized and ridiculed. (Give a thumbs up for those who share the same feeling!) There is absolutely no malice here, it is just a metaphor. If it is not appropriate, please ignore it! ! !
2. The test engineer must not only be able to test, but also learn network, linux, various development languages, databases, various frameworks, front-end, operation and maintenance, big data, products, etc. (I feel like I can’t list it at all! Ghost knows tomorrow What's coming out again), by the way, we have to learn the technique of tearing and pushing the pot, haha, it is a hodgepodge in the private chat between me and the students! ! ! Of course, some people may say that we have to learn this too, yes, so everyone learns a lot, so don't have anything to do with sarcasm and test. Why bother with each other if they are all technical! ! !
3. Okay, take a bite to calm down! It must be explained that any industry has three-six-nine-level hierarchies, just like elementary, intermediate, advanced, and expert, everyone and any industry needs a process to complete the transformation! Therefore, test engineers also start from the so-called non-content work, and all the big cows come in this way. People in all industries are the same! Is it better to have more encouragement and guidance without ridicule and ridicule?
4. At the beginning, we should be as objective as possible, so here I also want to express that if the test engineer has no technical content, if we want to get rid of this pot, we testers have to review themselves. I have also contacted many people, and quite a few of them feel that the test is simple and that's why they came! This thought is terrible! We test people have to work hard by themselves, we have to pay, less complaining, less mutual suspicion, more hard work, you can also become a big cow! Can the prospects be bad when all testers can work in one direction?
Take it for granted
Calm down your mood and take a look at the scene where the calendar is in the target:
The development progress has been postponed, but it must be online on time! Ok! Compress test time! Work overtime!
- Why is there a bug online? How did you test it! Well, test the back pot!
- Why don't you even know a log or sql! Well, this is indeed our problem, so everyone has to study hard. Many things are not just as useful as they are learned, but to reserve and expand their minds! (I once saw a product manager debugging ios code with a mac. What do you think of testing friends...)
- Why do you just have a little bit, can you do some tall technology! Well, sometimes we think too, you have to cooperate too, boss!
- . . . . . . (Too many, welcome everyone to add...)
When it comes to this issue, it is a bit big. In fact, in a complete R&D process and ecology, every link is important. Here I just want to simply talk about and test related:
1. Testing is not the last straw, but a vaccine to prevent it! After the vaccine, your chances of getting the disease are greatly reduced, but it does not mean that you will not get the disease. Therefore, please understand the test correctly to realize the value of ta!
2. The generation of a bug involves too many points, just as any development engineer dare not say that the program I wrote is okay! Sometimes it may be just a configuration, a change, or even forgetting to open the network port, causing a major bug! This not only requires the test engineer to take full account of the test points, but also the support of a complete and standardized online process! This is the same as making a car. A great person can't make a good car. It needs a lot of cooperation to complete it! So don't just blame the test! We really don't want to!
3. Sometimes it's not that we don't want to engage in high-level technology, it's that we don't get support, and even the leadership's perception is wrong! What do you want us to do? The workplace environment itself is complicated, and sometimes it's not that you are not good at failing, it may be that the environment does not match. For example, it is obvious that your ui becomes faster than the weather in Beijing, so let's do automated ui testing! Once it's done, you feel that the efficiency is not high! You must put the airplane engine on the tractor. What do you want me to say?
Okay, I'm a little excited, calm down! Nowadays, more and more systems are developed by separating the front and back ends. You will find that there is no id or name on the page. Basically, they are all unified class names. The events bound later, you can't even js. Now, this thing makes you very tired of ui automated testing! Therefore, technology doesn't care about its height at all, but uses it according to local conditions! Use the right place to be effective, otherwise it may bring bad news!
Is it worthy of being respected
In fact, there are still many things I want to say, but I know that if they say too much, they will definitely see fewer people, so I just stopped talking. Finally, back to the title, test engineers deserve to be respected! ! ! ! !
Of course, this respect cannot be spoken out of the mouth, but needs to be done by the tester. Any industry and anyone deserves respect (although it feels nonsense). The product is dedicated to designing a good product to generate benefits, the development is dedicated to writing code to create a molded product, the test is dedicated to finding as many bugs as possible to reduce unnecessary impact, and the operation and maintenance is dedicated to ensuring the system is good. Operation and operation are dedicated to keeping the products intact. In fact, each of us is dedicated to doing things, and everyone deserves to be respected!
If we can all affirm each other's value, encourage each other, and help each other even if there are shortcomings, then what is the scenario! ?Maybe it is the scene that all of us IT people yearn for!
Finally, I would like to apologize to everyone, because the above content may be a bit inappropriate or extreme. For testers, we must respect ourselves and our profession, strive to improve ourselves, and win respect with actions and examples; for non-testers, perhaps we should understand the test from a different perspective. We are indeed a group of simple, cute, hard-working little snails. Although carrying a heavy shell on his back, he is trying hard to climb up!
Finally: a wave of software testing data sharing!
In the technology industry, you must improve your technical skills and enrich your practical experience in automation projects. This will be very helpful for your career planning in the next few years and the depth of your test technology mastery.
In the interview season of the Golden 9th and the Silver 10th, the season of job-hopping, organizing interview questions has become my habit for many years! The following is my collection and sorting in recent years, the whole is organized around [software testing], the main content includes: python automation test exclusive video, Python automation details, a full set of interview questions and other knowledge content.
May you and I meet and you will find something! If you want to exchange experience in software testing, interface testing, automated testing, and interviews. Follow WeChat public account:[Sad Spicy Strips]Receive a 216-page software test engineer interview book for free. And the corresponding video learning tutorials are free to share! Communication learning skirt:313782132
Recommend good articles:
What exactly should I learn in automated testing?
Which is more advanced, automated testing or manual testing?
Novice must see: How to write a qualified test case?
Python login interface test problem record and solution (dry goods)