模板
教程
環(huán)境
性能
功能
管理
從測試策略到測試架構
今年是我做軟件測試的第7個(gè)年頭了，當年我從軟件開(kāi)發(fā)轉做軟件測試的時(shí)候，沒(méi)有想過(guò)我能在這個(gè)領(lǐng)域做這么久。
在這7年里面，我在軟件測試領(lǐng)域摸爬滾打，從自動(dòng)測試起步，逐步接觸到軟件測試的各個(gè)領(lǐng)域：各種測試方法（等價(jià)類(lèi)，全配對等）、測試技術(shù)（單元測試，功能測試，性能測試，探索性測試等）、自動(dòng)化測試工具（JUnit，Selenium，Gatling，ZAP等）、測試流程（傳統測試流程，敏捷測試流程等）以及測試策略（測試象限和測試金字塔等）。
其中“測試策略”在測試業(yè)界是討論的比較少的，因為大多數人的工作重點(diǎn)是設計測試用例，執行測試或者開(kāi)發(fā)和維護自動(dòng)化測試，而只有少部分人才會(huì )涉及到測試策略的工作，從而導致很多測試人員其實(shí)并沒(méi)有系統的了解測試策略。
所以我準備將我這幾年對于測試策略的經(jīng)驗、總結以及思考以系列文章的形式寫(xiě)出來(lái)，希望能稍微幫助一下大家去理解測試策略，從而做到更好的測試，減少缺陷，提高質(zhì)量。
測試策略
首先來(lái)看一下Wikipedia上對于測試策略的定義：
A test strategy is an outline that describes the testing approach of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing environment.
Test strategies describe how the product risks of the stakeholders are mitigated at the test-level, which types of testing are to be performed, and which entry and exit criteria apply. They are created based on development design documents. System design documents are primarily used and occasionally, conceptual design documents may be referred to. Design documents describe the functionality of the software to be enabled in the upcoming release. For every stage of development design, a corresponding test strategy should be created to test the new feature sets.
原文轉自：http://insights.thoughtworkers.org/from-strategy-to-architecture/
