Six Hats for Software Testing

skinapi

链接请见：
http://www.logigear.com/newslett ... oftware_testing.asp

Sometimes, when we are testing software, we need fresh ideas on where and how to test. For instance we may be stuck in a rut where we keep trying the same things with little or nothing to show for our efforts. Recently I have been using some great ideas from Edward De Bono who wrote an instructive book called Six Thinking Hats (1985 by Little Brown and Company. Updated edition 1999 by Back Bay Books). In the book he describes the individual hats: yellow for positive, black for negative, green for creative, white for factual, blue for control, and red for emotional thinking.

Each hat is used, one at a time, and we view the problem from that perspective. For instance with our red hat on we can safely focus on our emotions in relation to the software we are testing - how does it make me feel? Angry that the software seems so poorly finished, frustrated that we have no solid requirements, etc. Then we swap to another hat, such as the yellow hat which encourages positive thinking - if we can find and fix the performance problems then I think we will be able to ship the improved version to our clients in time to meet the project time scales, etc.

If we are working with others all of us use the same hat at once and we focus on applying that hat when thinking about the software we are testing, so we might spend five minutes doing some "green hat thinking" on creative new ways to test the software. For instance exploratory testing might help, particularly if we've been limited to mainly scripted-testing for the last few days.

Friends and colleagues have used the six thinking hats for software testing. For example, one colleague used it to include various stakeholders, including the non-technical end-users, for user-acceptance-testing for a web-based application. The users were able to comment on the strengths and weaknesses of the software, and suggest improvements, in a non-threatening way, all within an hour's meeting.

Why not give the "six thinking hats" a try on your current project? You can learn the concepts within an hour and try it for an hour.

Erica

Six Hats for Software Testing
软件测试的六顶帽子

Sometimes, when we are testing software, we need fresh ideas on where and how to test. For instance we may be stuck in a rut where we keep trying the same things with little or nothing to show for our efforts.
有时，当我们在做软件测试的时候，我们需要刷新我们的思路来测试哪里或如何测试。例如，我们总是陷入一种几乎一样的路子而简直没有展示出自己的努力。

Recently I have been using some great ideas from Edward De Bono who wrote an instructive book called Six Thinking Hats (1985 by Little Brown and Company. Updated edition 1999 by Back Bay Books). In the book he describes the individual hats: yellow for positive, black for negative, green for creative, white for factual, blue for control, and red for emotional thinking.
目前我已经使用了一些很棒的方法。这些方法在Edward De Bono写的名为六种思考的帽子一书中。书中分别描述了这几顶不同的帽子：积极的黄色、消极的黑色、富有创造性地绿色、事实性的白色、控制性的蓝色和情绪化思考的红色。

Each hat is used, one at a time, and we view the problem from that perspective. For instance with our red hat on we can safely focus on our emotions in relation to the software we are testing - how does it make me feel? Angry that the software seems so poorly finished, frustrated that we have no solid requirements, etc. Then we swap to another hat, such as the yellow hat which encourages positive thinking - if we can find and fix the performance problems then I think we will be able to ship the improved version to our clients in time to meet the project time scales, etc.
每个人每次使用一顶帽子，并且我们使用其中的观点看法来审视问题。比如，红色的帽子，我们能把我们的情绪集中在我们正在测试的软件上，或是这个软件给我的感觉如何？愤怒，这个软件完成的非常糟糕、失败，这些归结为我们没有可靠的需求等等。然后，我们换了一顶帽子。比如黄色的帽子，它鼓励积极的思考-如果我们能找到并解决性能问题，我想我们就能发布改良的版本给我们的客户以满足项目的时间限制等

If we are working with others all of us use the same hat at once and we focus on applying that hat when thinking about the software we are testing, so we might spend five minutes doing some "green hat thinking" on creative new ways to test the software.
如果大家工作的时候突然戴同样的帽子，并且当我们考虑正在测试的软件的时候我们就把注意力集中在了帽子上，因此，我们也许会花费5分种的时间做些关于创造新的软件测试方法的“绿帽子思考”.

For instance exploratory testing might help, particularly if we've been limited to mainly scripted-testing for the last few days.
比如探测性测试也许有帮助，特别是在后期如果我们用脚本进行测试的时候。

Friends and colleagues have used the six thinking hats for software testing. For example, one colleague used it to include various stakeholders, including the non-technical end-users, for user-acceptance-testing for a web-based application.
朋友和同事已经使用“六顶思考的帽子”进行测试。比如，一个同事使用这些帽子把不同的赌金保管者包括在内，对于用户可接受的测试和基于web的应用来讲，还囊扣了无技术的最终的用户。

The users were able to comment on the strengths and weaknesses of the software, and suggest improvements, in a non-threatening way, all within an hour's meeting.
用户能够评论软件的健壮性和缺点，并且提出建议改进，这种改进是无风险性的，所有的这些都在一个小时的会议中提出。

Why not give the "six thinking hats" a try on your current project? You can learn the concepts within an hour and try it for an hour.
在你当前的项目中，为什么不尝试的试一试“六顶思考的帽子”呢？你能够在一个小时中就学会概念，然后再用一个小时去尝试他们。

[ 本帖最后由 Erica 于 2006-5-29 11:08 编辑 ]

skinapi

谢谢Erica，加分鼓励了。

skinapi

那sunming感觉翻译成什么比较好

Erica

欢迎批评指正!

jackei

其实很多六顶思考帽的课程都会安排练习，当你和一个6人团队练习过之后，你就会体会到它的作用了。

当然，也可以理解它就是让你从不同的角度和方面去思考问题，更全面的思考问题。

szhu

one colleague used it to include various stakeholders, including the non-technical end-users, for user-acceptance-testing for a web-based application.

The users were able to comment on the strengths and weaknesses of the software, and suggest improvements, in a non-threatening way, all within an hour's meeting.


这一段是否这样会好一些？

一位同事运用了这种方法， 将项目的各类参与者， 包括非技术性的终端用户， 都纠集来做一个基于互联网的应用软件的用户可接受测试。

用户们得以用一种不咄咄逼人的方式来点评这个软件的强项与弱点，并提出改进建议。 所有这些， 都在一个小时的会议中得以完成。

[ 本帖最后由 szhu 于 2006-5-31 20:14 编辑 ]

Erica

非常感谢szhu 的点评。

szhu

No problem, let's learn together.