Two treasure maps and three layers of software testing

Software TestingThe treasure map differs greatly from my software test panorama (for example, process-based software test Panorama), with a much richer content that covers all the knowledge points. In my panorama, I ignore the details and general knowledge, emphasize the connotation and test the internal relationship of each link. The logic is clear and practical, and each has its own merits.

IntegrationPerformance TestingTo describe the three layers of software testing engineers. This description is more vivid and specific, and easy for the team to accept and understand.

The software testing dashboard diagram was drawn by Stas Consulting Inc. CEO Wonil of South Korea and printed as a poster map. The English version (from the Public Information http://sites.google.com/site/swtestingmap/stadventure) is attached here ). Although not clear, the copyright belongs to sta Consulting Inc.

 

Based on the above treasure map, search on the Internet and find another software test treasure map with richer content provided by deltaaxiom. You can access "unique series of posters from Delta axiom-SoftwareTestingAt a glance-or two "downloads a PDF file.

However, it is difficult to find out which of the above two software test charts is the first and which one is the reference?.) No matter what, it is a good idea, using a picture to describe all the knowledge points of software testing and their relationships is helpful for us to better understand software testing. In addition, we cannot translate it into Chinese because it is not authorized yet. If we have time in the future, we can develop a Chinese version of the software testing diagram.

　　Full Graph

 

 

Upper right

 

The three levels of software testing Engineers (Entry/middle/senior) are described by Microsoft's principal SDET Adam Millard. In addition, he paid great attention to the speed of speech (so that everyone can hear clearly). The authentic American language was impressive, so that all the audience could be pleasing to the eye.

From the perspective of test engineers, there must be a clear goal to develop from entry level to intermediate and senior level. That is to say, to what level is it senior? Of course, it is not determined by the working life. If the technology, communication, business understanding, project control and other capabilities are not up, the impact scope is small, and the service life is longer, it may still stay at the entry level or intermediate level. Here we provide Adam's three slides for your reference to help you understand the competency requirements at different levels.

He also talked about the differences between Chinese and American cultures. For example, in China, the career goals of technical management are more attractive, and managers (team contributions) are paid much better, while individual contributor (personal contribution, it is relatively difficult to develop career paths (career path) by a pure technical senior engineer. In most companies in the United States, the two career paths are relatively balanced, the salary of a senior engineer can be higher than that of the Manager/Director. Some people like technology, do not manage, do what they like, and the development is not affected.