Software Test Architect is a new position, but it is a very necessary job, the main points:
1. In accordance with V model, generalized testing concepts, etc., (static) test sooner, found defects sooner, the better quality products, accelerate product development cycle and reduce costs. More importantly, the prevention of serious design flaws, if the design defects, when the system is set testing found the problem, rework caused would be awesome. This requires design review, review, and in this process, the need to test personnel involved.
2. For the current systems become more complex, whether J2EE or .Net framework architecture, whether it is centralized or distributed network system system, whether it is the host system or server cluster system, its design is often not easy, but also based on previous experience in the design, based on lessons learned (problems found) optimized system configuration.
3. The more complex software systems, providing more functionality, the higher the test requirements, which determines the system must have good testability, which is guaranteed by the development and design architect, not very insurance.
4. Test system performance, security, stability, reliability, there are high demands on the technology platform environment configuration, system deployment.
As a software testing architect, whose main responsibilities are:
1. Review system architecture design, system component / component interfaces and their relationship to
2. Ensure that the system testability
3. The method of testing strategies and design software systems, especially in terms of system performance testing methods, security, stability, reliability, technological lines and quality standards
4. component complex system test environment, and to analyze and solve technical problems deeper (Troubleshooting) appear in the test and help make defective isolation
The recommendation system (performance, security, stability, reliability) test to analyze, evaluate, and proposed to improve the performance, reliability and design modifications, a refactoring
6. design of test automation technology framework, presided over an important tool for the study of the test, assessment, design
7. Participation System Deployment Design
8. involved in the assessment and introduction of new technologies
9. help improve the testing process, improve test efficiency
At the same time, the recruitment of software testing architect, but it is very difficult, the main reasons are:
1. For a good majority of engineers, architects, less on process management, testing strategies and methods, quality attention, understanding, lack of good attainments or RUP CMM / CMMI area. The test engineers on the technology less opportunity, hard enough, not enough technical knowledge, it has a system architecture and test methods, and many a man of great ability, is small.
2. At present, the industry there are still prejudices, with superb technology and rich experience of technical personnel, more willing to do development, not willing to do the test, a phenomenon occasionally reflected in the company's salary system, or the management of this company inadequate attention, lack resolution.
3. domestic professional test development relatively late, in the natural talent market, experienced, professional test engineer is not much, let alone skilled Test Architect.
4. Software Test Architect positioning is not clear, companies do not give clear responsibilities and job content.
The technical staff increases with age, tend to management development, most enterprises policy is also directed towards this area. Deputy example, managers and other management positions with high salaries than purely technical personnel. Actually, the majority of foreign-funded enterprises, a strong technical staff (architects) entirely possible above his / her supervisor.
【Editor's Choice】
Source document < http://developer.51cto.com/art/201104/254069.htm >
What is a test architect?
Matthew Heusser recently asked What is a software architect anyway? Matt when on to ask what a test architectdoes. This question was so good (and the answer so long), that I thought I'd respond here.
So, what is a test architect. One answer is that it's a fancy title for an experienced tester. At Microsoft, we try to avoid this definition, and instead describe test architect as a senior test role with wide strategic scope. That's the short answer.
Here's the long answer.
There is no “typical” test architect role. Test architects focus on a diverse set of goals and perform a wide variety of tasks. Some spend time developing testing infrastructure, test authoring frameworks, or evaluating features in order to create complex tests. Some are in charge of a particular technology for their group. Others spend time consulting on how to improve test effectiveness. The common thread across all test architect roles and the primary responsibility of a test architect is to provide technical leadership and strategic direction for their testing organization. It is also expected that in addition to accountability to the current product, that senior test architects will consistently look beyond the current release and may have several deliverables not tied to a particular product release.
A test architect has in-depth knowledge of a variety of testing techniques and methodologies used both inside and outside of Microsoft. They often provide technical assistance and/or advice to the test Manager. The question often arises - “Shouldn’t the test manager be doing all of this anyway?” Typically, the test Manager is the individual providing leadership and formulating team strategy. However, as organization sizes continue to grow and/or the test manager takes on additional responsibilities, it often makes sense for a test architect to step in and assist with or deliver on these responsibilities. The test architect often takes on some leadership roles typically associated with the test manager. For example, while test managers certainly will implement change to grow their teams, the test architect is frequently the individual who provides technical leadership and strategic direction for their organization.
A test architect is expected to be able to affect change not only across the testing community, but between other engineering disciplines as well. Test architects must drive quality across all disciplines, providing guidance, feedback, and suggestions to improve quality practices across an entire engineering team.
While a few test architects may be focused on a specific problem or improvement, the goal for the test architect investment should be long-term improvement of the organization testing process and growth. Senior test leaders, when faced with an urgent problem or situation in need of quick improvement can typically find a solution. Broad or recurring issues, however, may require a test architect. The test architect should be thinking long-term and laying out a path for solving big issues over a long period and not focused on fighting daily fires. The test architect must be focused on defining the testing process and setting the test team up for continued success.
源文档 <http://blogs.msdn.com/b/alanpa/archive/2008/05/01/what-is-a-test-architect.aspx>
Test Architect
By John Morrison on Oct 08, 2007
源文档 <https://blogs.oracle.com/johnmorrison/entry/test_architect>
转载于:https://www.cnblogs.com/henryhappier/p/3216921.html