Suddenly, it seems that many people want to apply for test development and testing. Many people will also be asked about the differences between these positions during interviews. Then there are very few people who have testing experience or have systematically studied testing. The poster was also very confused when applying for this position last year. I have consulted several big bosses and seniors on the Internet. Here is a small summary.
The main content comes from the conversations with the big guys and the book "How Google Test Software", (if there is any inaccuracy, you can comment and talk about it), and I hope that friends who were as confused as I was at the time can gain something.
Let’s clarify the abbreviations first. After all, these names are too similar, and Chinese is easy to confuse. Software Development Engineer (SWE), Test Development Engineer (SWT), Test Engineer (TE).
the difference
SWE also needs to do testing work. SWE needs to write test-driven design, unit tests, and participate in the construction of tests of various sizes.
SWT is also a developer role, but the focus is on testability and the general testing infrastructure. (SWT also needs to be able to write codes. Code requirements are not lower than development. The focus of their code writing is testing. PS: Take bytes as an example. Most of the test development is a technical sequence. The code requirements are consistent with the development, and the salary is also the same (at that time, the lecture will be listened to)).
SWE and SWT are not enemies (not a production bug, but a nitpicking one), they are more partners. The purpose of SET writing code is to allow SWE to test its own functions.
TE puts users first in thinking, organizes overall quality practices, analyzes and interprets test run results, drives test execution, and builds end-to-end automated tests. (SWT and TE work are intertwined a lot. SWT is more about building a test framework and writing test tools. TE is more about scripts, test cases, and a little bit...
Taking bytes as an example, TE has relatively low requirements for code, but it also needs to write code (you will listen to the lecture)).
Many test developers in domestic manufacturers actually do testing, and many test developers do development work. These all depend on your team and cannot be generalized.
SWT and TE have higher requirements for the breadth of knowledge. For SWE, you may only need to study carefully from one angle. For SWT and TE, you need to be a "universal doctor". As the author of the recommended book said, it is often more difficult to recruit a good SWT and TE than SWE.
The ceiling of SWT may be lower than that of SWE (after all, the domestic fact is that SWT and TE are rarely the main program), but it is an indisputable fact that SWT is getting more and more attention, and the average salary of SWT is not low.
feature
In the end, choose SWT or TE to quote several standards (excerpts) in the recommended book (this is also a few big guys who communicated and repeatedly mentioned whether they really like testing work).
You may be a SET if you have the following characteristics:
1. When you are programming, you will feel guilty that there are still many unit test cases that have not been completed. Then, you consider various ways of generating test code and verification, rather than writing each unit test case by hand.
2. Get anxious when you see compiler warnings.
3. When asked to test a product, you open the source code and start thinking about what needs to be simulated.
4. The leadership you have in mind is: build a great low-level unit testing framework for everyone to use, or run millions of times a day on the test server.
5. When asked if the product is ready to go live, you might say: All tests passed.
You may be a TE if you have the following characteristics:
1. You can quickly find errors in existing code segments and quickly understand software failure modes, but you don't care about writing code from scratch or making modifications.
2. You are more willing to go to some open source websites to read other people's source code.
3. You are willing to communicate with other people in the real world.
4. The leadership in your mind is to support the ideas of other engineers and challenge their ideas with application scenarios of higher order of magnitude.
6. When asked whether the product can be launched, you may say: I think it is ok.
Summarize
To sum up (the high probability is like this, please don’t get into the horns, there is no such thing as good or bad):
-
Code capability requirements: SWE=SWT>TE
-
Knowledge breadth requirements: SWT/TE>SWE
-
Communication skills requirements: TE>SWT>SWE
-
Knowledge depth requirements: SWE>SWT>TE
-
Salary: SWE=SWT>TE (pure development, testing and testing, of course, many companies in China can’t figure out the difference between these titles)
Finally: In order to give back to the die-hard fans, I have compiled a complete software testing video learning tutorial for you. If you need it, you can get it for free【保证100%免费】
Software Testing Interview Documentation
We must study to find high-paying jobs. The following interview questions are the latest interview materials from first-tier Internet companies such as Alibaba, Tencent, and Byte, and some Byte bosses have given authoritative answers. After reading this set of interview materials, I believe everyone can find a satisfactory job.
