In the world's top enterprise, software testing engineering is how testing is done.
------------------------------------------------------------------------------------------------
1. The meaning of the job title:Even if you give a rose a different name, it may still smell the same. However, if you give engineers different job titles, their understanding of their responsibilities will be very different. Microsoft collectively refers to software engineers who develop product features by writing code as " Software Development Engineers" (SDE). The official job title of Microsoft Test Engineer is "Software Development Engineer in Test" (SDET). The two titles sound similar because Microsoft's test engineers also do development at the same time. Other major responsibilities of a test engineer include: developing test plans, designing test cases, analyzing the root cause of defects, participating in program code reviews and product design reviews, and developing test automation programs. Sometimes test engineers also participate in the development of the product source code, or the correction of defects. But in general, because of the heavy workload of test engineers, it is not very common to be directly involved in product development.
Hiring software engineers with a passion for testing to do testing is a proven innovation at Microsoft that is completely different from what other companies in the software industry do. It is often concluded that we hire engineers who can write code to do testing because we want them to write effective automated tests that exclude manual testing. In fact, this is only a small part of the reason. Those test engineers who know how to write programs and the basic structure of computers often have the analytical skills necessary for software testing. Their ability to detect defects early and analyze their root causes allows them to find similar defects quickly. Having the same computer base as development engineers enhances the skills of test engineers and gives our test engineers more flexible and dynamic productivity.
Before 2005, Microsoft divided software testers into: software test engineers (Software Test Engineer, STE) and software development test engineers (SDE/T). The division of labor between SDE/T and STE.
It can be seen that STE's work is closer to the work of our general black-box testers, focusing on test plans, test cases, test execution and design review; while SDE/T's work is to develop test tools (safety). , performance, development of automation tools) and general testing work such as finding bugs, participating in design review, code review, etc. (ps: Only Daniel company will set up testers who develop test tools, huh)
After 2005, Microsoft adjusted the title of testing and collectively referred to all testers as: Software Test Development Engineer (SDET)
Microsoft's SDET training roadmap:
2. Microsoft Test Architect
Microsoft established the title of test architect in 1999 . It's designed for high-level independent contributors who have an impact on the product. The title of Test Architect reflects the broad influence of an SDET on the products it works on. The titles of senior SDET , chief SDET , and partner SDET are mainly given to those who have an impact on the function of a product.
Remember, though, that the test architect is a role, not a position. Although a senior test engineer may be promoted to test architect, not everyone will become a test architect. Often, some departments create a test architect role for business or strategic needs. But sometimes you also see a senior test engineer playing the role of a test architect, but without the title of test architect. Note that the role of Test Architect is discussed here and not the title of Test Architect.
Microsoft does not have a universal or representative test architect role. Test architects at Microsoft work on a variety of goals and take on a variety of tasks. Some people spend time developing the basic structure of tests, testing frameworks, or evaluating product functionality and creating complex tests. Some are responsible for managing a particular technology in their department. Others are in charge of consulting on how to improve testing efficiency. The common and primary responsibility of all Test Architect roles is to provide technical direction and set strategic direction for the department. The level of test architects usually indicates their area of responsibility - whether they are working on a set of features of the product, a product line, or spanning an entire department. Of course, in addition to being expected to be accountable for an existing product, the test architect should also be able to look beyond the current version of the product and, if possible, have two or three outcomes that are not directly related to the release of a particular product.
Microsoft's test architects have to effectively influence not only the testing world, but also development and project management. The Test Architect must be able to drive the quality of the product, provide guidance, feedback and recommendations to improve quality specifications across the engineering department.
We talked about the "what" of the test architect, so what is the "not" of the test architect? The title of Test Architect is not awarded based on level or experience. Setting up a test architect is an investment. This investment is combined with the market's need for talent who can help make flexible changes to the product. It's worth emphasizing that Test Architect is not a career track. Skill requirements for test architects are consistent with career stage development requirements for other roles at similar levels, both emphasizing cross-organizational communication and the ability to drive change. hint:
As of 2008, there were only forty test architects out of Microsoft's more than 9,000 test engineers worldwide.
Three, Microsoft's testing career development path
1. Career progression from SDET Independent Contributors
The scope of influence extends from a narrowly defined product feature to a family of product features, a complete product. Such as Microsoft Office Word or Microsoft Media Player, until finally reaching a product line, such as Office or Windows systems. Influence can extend horizontally based on various aspects of testing, like a test architect position, or vertically based on a technical area like protocol security.
Partner SDET is not the highest point of an engineer's career development track, but the highest point of a test career development track. Partner SDET is one level below Distinguished Engineers (equivalent to corporate vice president level). This is not because Microsoft feels that there is no need for outstanding engineers in testing, but we believe that as engineers continue to advance their career paths, their behaviors become more and more similar, and the differences between different disciplines bring about Impact value is decreasing. In a sense, every engineer who works in any of the 10 engineering disciplines can reach the level of being an engineer in another discipline as their technical field develops.
2. A brief introduction to the career development process developed from SDET management
At Microsoft, when an engineer moves to a management position, it's a " level " change , and moving to a manager doesn't mean you have a higher salary, a better office environment. That is to say, Microsoft has technical staff with senior technical background, and they also share technical work while managing.
It is important to note that technical sophistication and his skill level are far more important than the size of the test group he manages in determining whether an SDET supervisor can continue and develop in his career path. A group responsible for testing product safety is an example. These small but highly technical groups often have a significant impact on the quality of the product, so in such groups you may often find a more senior SDET executive. In a relatively small group, the SDET director himself has to do a lot of testing, programming, analyzing, and documenting software vulnerabilities. Every member of the product team, from the most senior executive director to the newly hired employee, should keep a bug log on file when a product bug is discovered. As a group grows larger, supervisors need to take on more management responsibilities and spend less time on specific technical work. Regardless of the size of the group, SDET supervisors should have strong technical skills, and at the same time, they should also be responsible for the technical leadership of a group. SDET supervisors are usually the engineers who know the most about a product function in the group, and they are also the best in the group. One of the testers and developers.
3. Title of Test Manager
Test managers rarely need to do specific testing tasks themselves, such as writing and executing test cases. But everyone in the field of testing, no matter what level he is, will find software defects by himself. Test managers still need to be technically savvy, but they are required to focus more on establishing testing processes and tools rather than on specific functional tests.
----------------------------------------------------------------------------------------------------------------------
personal opinion:
1. The question of whether testers need to understand development is a question discussed by many testers. In my personal opinion, when the test reaches a certain depth, there will be bottlenecks. If you want to go further, learning and development is a breakthrough. I don’t think I understand it. The developed test is like "tickling the clothes", what does it feel like? Experience it for yourself! Tips and must be proficient in development, but must have development thinking. Maybe Microsoft's products are special, so all their testers have become SDET (software testing and development engineers), since it exists, it has its meaning, and it still exists in such a fork company, hoping to be a small junior tester like me It is a goal to work towards.
2. Microsoft's engineers transfer to management positions are "level", and to transfer management must be technically superior to colleagues. It can be seen that Microsoft regards technology very important. As far as I know, the testers are relatively impetuous. The content of the work is scattered but not deep, and the salary is relatively low compared to the developers, especially the testers who have just entered the industry. Many companies have not given a good position, and the career development is relatively confused. This is the current situation of our testing industry, but I still hope that you will be calm. Focus on technology.
(The above personal views, welcome to Paizhuan~! Ha ha)