軟體測試3.0

LogiGear 的一份白皮書 whitepaper 《 Software Testing 3.0 - The Continuing Evolution of Software Testing 》中把軟體測試的發展定義為 3 個階段，在我看來現在很多軟體企業還在第一個階段“摸索”著！

 

Software testing has already gone through at least two clearly identifiable phases. In “Software Testing 1.0 ”, software testing was misunderstood. It was an afterthought or adjunct to the development process left to less skilled, lower-paid individuals who actually viewed software testing as the entry point on a career path to becoming a software developer. There were few useful testing tools and methods for achieving a high degree of automation. Those that existed were expensive, complex, difficult to use, and ineffective at addressing productivity needs and concerns. In this phase, executive management was mostly disconnected from software testing – assuming that somehow, it would get done.

 

軟體測試已經走過了兩個清晰的階段。在 1.0 階段，軟體測試常常被誤解，測試往往是被忽略、不受重視、待遇低，從事軟體測試的人往往把測試工作當成是走向軟體開發的入口點。在這個階段，鮮有測試工具和方法可以達到高水平的自動化。

 

With “Software Testing 2.0 ” came the recognition that software testing was and is an important part of the development process. Software testing was recognized as a valuable part of application development, and everybody started to test in earnest. With the high degree of acceptance across functional groups, came ownership issues – issues of where testing fits organizationally, how it is budgeted for, and from where testing should receive its direction. There was also an explosion of available tools. These tools often further distracted the testing efforts, turning the process into one of tool selection without clear goals, architecture or direction. Within this phase, executive management’s understanding of testing was still rudimentary as was their involvement.

 

在 2.0 階段，大家意識到軟體測試是開發過程中的一個很重要的部分。在這個階段，對於工具的選擇沒有清晰的目標、架構和指引。

 

Software Testing 3.0 starts with the understanding that testing is still valuable to the organization. The foundation for Software Testing 3.0 is a strategic end-to-end framework for change based upon a strategy to drive testing activities, tool selection, and people development. Fundamental to its success is the realization that testing is its own function, and an integral part of the development process. Testing must have its own budget to build the necessary infrastructure, as well as clear leadership and ownership. It must provide executive management with visibility into the status of the software under test so that executives can make intelligent and informed decisions about projects and have confidence that they are developing and delivering a quality product that will meet customer needs.

 

在 3.0 階段，基於策略驅動測試活動、工具的選擇和人員開發。意識到測試需有自己的預算，從而構建必要的測試框架，要有獨立的自主權和領導權。測試需要為管理層提供清晰的關於被測軟體的狀態，以便管理層能夠做出英明的專案決策，並且給他們信心 – 我們正在開發和釋出能滿足顧客需求的高質量的產品。