轉(zhuǎn)：https://www.cnblogs.com/henryhappier/p/3216921.html

軟件測試架構(gòu)師是一個新職位，但確實是一個非常必要的職位，主要有幾點：

1. 根據(jù)V模型、廣義測試概念等，(靜態(tài))測試的越早，發(fā)現(xiàn)缺陷越早，越有利于產(chǎn)品的質(zhì)量、加快產(chǎn)品開發(fā)周期、降低企業(yè)的成本。更重要預防設(shè)計出現(xiàn)嚴重的缺陷，如果設(shè)計出現(xiàn)缺陷，在系統(tǒng)集測試發(fā)現(xiàn)問題時，所造成的返工將是可怕的。這就需要對設(shè)計進行復審、評審，而在這過程中，需要測試人員參與。

2. 對于當前系統(tǒng)越來越復雜，不管是J2EE架構(gòu)還是.Net架構(gòu)，不管是集中式網(wǎng)絡(luò)系統(tǒng)還是分布式系統(tǒng)，不管是主機系統(tǒng)還是服務(wù)器集群系統(tǒng)，其設(shè)計往往不是一蹴而就，而且要基于以前的經(jīng)驗進行設(shè)計，根據(jù)教訓(發(fā)現(xiàn)的問題)而優(yōu)化系統(tǒng)結(jié)構(gòu)。

3. 軟件系統(tǒng)越復雜、提供的功能越多，其測試要求越高，這就決定系統(tǒng)必須具有良好的可測試性，這一點通過開發(fā)設(shè)計架構(gòu)師來保證，不是十分保險。

4. 系統(tǒng)的性能、安全性、穩(wěn)定性、可靠性等的測試，在技術(shù)、平臺環(huán)境構(gòu)造、系統(tǒng)部署上有很高的要求。

作為軟件測試架構(gòu)師，其主要責任是：

1. 審查系統(tǒng)架構(gòu)、系統(tǒng)構(gòu)件/組件及其接口關(guān)系等的設(shè)計

2. 確保系統(tǒng)的可測試性

3. 設(shè)計軟件系統(tǒng)的測試策略和方法，特別是在系統(tǒng)的性能、安全性、穩(wěn)定性、可靠性等方面的測試方法、技術(shù)線路和質(zhì)量標準

4. 構(gòu)件復雜的系統(tǒng)測試環(huán)境，并分析、解決測試中出現(xiàn)的較深的技術(shù)問題(Troubleshooting)和幫助做好缺陷的隔離

5. 對系統(tǒng)(性能、安全性、穩(wěn)定性、可靠性)測試作出分析、評估，并提出為改善系統(tǒng)性能、可靠性而進行設(shè)計修改、代碼重構(gòu)的建議

6. 設(shè)計測試自動化的技術(shù)框架，主持重要的測試工具的研究、評估、設(shè)計

7. 參與系統(tǒng)部署的設(shè)計

8. 參與新技術(shù)的評估和引進

9. 幫助改進測試流程、提高測試效率

同時，招聘軟件測試架構(gòu)師，卻是非常困難的，主要的原因有：

1. 對于大多數(shù)技術(shù)很好的工程師、架構(gòu)師，對過程管理、測試策略和方法、質(zhì)量等關(guān)注較少，理解不夠，缺乏良好的RUP或CMM/CMMI方面的造詣。而測試工程師在技術(shù)實現(xiàn)上機會較少、努力不夠，技術(shù)功底不夠，所以具有在系統(tǒng)架構(gòu)和測試方法等多方面能力很強的人，是不多的。

2. 目前國內(nèi)業(yè)界還存在偏見，具有精湛的技術(shù)和豐富的經(jīng)驗的技術(shù)人員，更愿意做開發(fā)，不愿意做測試，這種現(xiàn)象偶爾表現(xiàn)在公司的薪水體系上、或者企業(yè)的管理層對此重視不夠、決心不夠。

3. 國內(nèi)測試專業(yè)發(fā)展比較遲，自然在人才市場上，有經(jīng)驗的、專業(yè)的測試工程師就不多，更何況是技術(shù)精湛的測試架構(gòu)師。

4. 軟件測試架構(gòu)師定位不清楚，企業(yè)沒有給出清楚的責任和工作內(nèi)容。

5. 技術(shù)人員隨著年齡增大，傾向于向管理發(fā)展，多數(shù)企業(yè)的政策也是向這方面引導。例如副總、經(jīng)理等管理職位薪水要比純技術(shù)人員高。實際，在多數(shù)外資企業(yè)，很強的技術(shù)人員(架構(gòu)師)完全有可能高于他/她的上司。

【編輯推薦】

2.6.1 測試架構(gòu)師

架構(gòu)師是怎樣煉成的

從技術(shù)層到管理層修煉之路：架構(gòu)師

架構(gòu)師最怕程序員知道的10件事

測試專家講述通往測試架構(gòu)師之路

?

源文檔?<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.

?

轉(zhuǎn)載于:https://www.cnblogs.com/shyshy/p/11054858.html

總結(jié)

以上是生活随笔為你收集整理的什么是软件测试架构师？的全部內(nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯，歡迎將生活随笔推薦給好友。