Test experts on the road to test architects

As I learned more and more about the testing profession, I learned more and more about Microsoft's testing technology. Slowly, people began to be interested in what those testing experts are doing. They are a small number of people in the company with the title of "test architect.

AD: wot2014: user tag system and user data operation training session

 

I have been in the company for several years. I have gained a lot of skills in testing technology and can enjoy the pleasure of writing code. My colleagues often share their opinions on software testing technology, I also realized some innovative Testing Techniques in the project and a well-designed testing framework based on my own ideas. I am very happy every day. As I learned more and more about the testing profession, I learned more and more about Microsoft's testing technology. Slowly, people began to be interested in what those testing experts are doing. They are a small number of people in the company with the title of "test architect. They are test instances ts.

What? Is there a test architect in your company? Well, it seems that many people will ask this question. I heard a lot from architects. For example, Bill is named "chief software architect of Microsoft ". Generally speaking, when it comes to architects, people think of "software design architects". Those masters who design the entire product architecture, decide how to coordinate the work of each module, and decide which development platform to adopt (sorry, maybe everyone has different definitions of masters. If you only have talents like Lippman, stroustrup, and Anders in your mind, forgive me for my definition, my masters are the masters in the jeidi warriors. Some of them are super powerful like Yoda/Anakin, but there are also some common people who can learn a lot from them every day. I would like to call the latter a master .). So who are the "test architects? Why do they have the same salary as the design architect? How can we grow into a test architect? I also had such a problem that I had the honor to meet a test architect, Eide, at the redimon headquarters. That day, the weather was fine, benefiting the West.

Test architect. Here I will discuss the role's responsibilities rather than the title itself. So you may have assumed this role, but you do not have this title. But this does not prevent us from discussing what the test architect is doing.

If you are a test architect, it means that you have many things to do, although you may not do all of them: develop and design the test framework Test Library; Consider the features of the product globally, design a complex testing system, develop a specific testing technology, and consider how to improve testing efficiency for your company. But in general, we can describe it as follows: the test architect leads the development of the company's testing technology and the direction of the testing strategy. The difference between a test architect and a general test engineer is that he is concerned with a functional module, a product line, or the entire company's testing department. Even for some more senior test architects, they are no longer limited to testing the current version of the product. They can proactively consider the testing strategies and technologies of future versions.

The role of the test architect can be compared with the role of the design architect. The design architect, plan/design a product, and focus on the R & D process of the product. Similarly, the test architects plan/design the test platform and focus on the product testing process. (Not nonsense, right ?) However, they have a common feature that envy our IT migrant workers. They provide consulting services rather than helping you write every line of code. Their salary is determined by the number of words they typed.

The test architect has strong knowledge in the testing technology testing methodology, not only the internal knowledge of the company, but also the external knowledge of the company. Therefore, they have the strength to provide "consultation" services to test managers and tell them what testing technology and what testing platform will meet the company's requirements for product measurement, what kind of software process can better ensure the software quality. Some people will naturally think that this is not a test Manager thing? Otherwise, we all know that when people reach the "manager" position, there will be more chores, employee salary increases, employee benefits, office decoration, and test lab to buy new machines. Everything can be found at the head of the test Manager. The main responsibility of the test Manager should be to lead and train an excellent test team. Therefore, leadership and training are his key points. For the remaining tasks in testing technical testing strategies, the test architects around him played a complementary role. I think such an explanation can put a lot of test managers at ease and put all the technical and management burdens on the test Manager.

Test architects not only need to influence the testing community of the testing organizations in the company, but also the development institutions and even marketing departments. Good test architects can ensure the quality, exert a far-reaching and correct impact on all aspects of product R & D and sales, and also absorb suggestions from various departments to ultimately improve the overall software quality. Therefore, an excellent test architect can also be a good design architect and a good user demand analyst. Software Quality Assurance is a process that runs through requirement analysis, design, and testing of the entire software project. If you are a test architect, you must be able to control all stages of the software project. Therefore, familiarity with development and other departments is essential.

We have already talked about what so many software test architects "do". Finally, let's talk about what they "don't:

1. They are not project managers. Although they have mentioned that many software test architects impose influences on all aspects of the project, they are not project managers. There are still many things to consider for a pure project manager. If a test architect finally plays the role of the project manager, it is not beneficial to the project or the test architect.

2. The test architect is not a natural title. If you have been doing tests for many years and have a good understanding of the product, you will naturally become a test architect. You need to have enough technical foresight and influence on the company to provide consultation on product testing strategies and technical directions.

3. Not only is it a pure software testing technical programming expert, but a testing architect's existence is to solve the test problems in the actual project product, and is not a pure testing technical programming enthusiast. A person who is keen on the unit test and development framework can be a good programmer, but not necessarily a testing architect required by the Company. An architect is skilled in solving practical problems in both technology and testing strategy testing methodologies.