软件测试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 阶段，基于策略驱动测试活动、工具的选择和人员开发。意识到测试需有自己的预算，从而构建必要的测试框架，要有独立的自主权和领导权。测试需要为管理层提供清晰的关于被测软件的状态，以便管理层能够做出英明的项目决策，并且给他们信心 – 我们正在开发和发布能满足顾客需求的高质量的产品。