Fastpoint
级别: 总版主
精华:
44
发帖: 5033
基地声望: 390 点
基地币: 1689 Bug
基地贡献: 0 点
好评度: 15 点
在线时间:818(小时)
注册时间:2005-10-08
最后登录:2008-07-22
|
Discussion about exploratory testing.
Discussion about exploratory testing.
Exploratory testing is like a chess game with a computer. You revise your plans after seeing the move of your opponent. Yet all your plans can be changed after one unpredictable move of your opponent. Can you write a detail plan for a chess game with a computer? Let us think about how a chess master plays with a computer.
Does he write a detailed plan (he may have to write thousands of pages)? No, but he uses all his knowledge and experience. He can define only the fist move in the game and it is unreasonable to plan far ahead. You can plan 1 move ahead, or 20 moves if you're a very experienced player, but you can't plan the whole game. To plan 20 moves he had to spend a lot of his valuable time (the clock is ticking).
Of course he is trying to find some information about existing situations between moves. This is exactly what an experienced exploratory tester does.
After running any test case, testers may need to find additional information about application and system from a developer, system architect, business analyst, or may be from literature. A lot of information is necessary for correct exploratory testing. We are not testing an application that is written by a team of 10 or 20 developers. We are testing an application that was build by the whole Microsoft team if the applications work on Windows OS. Other teams whose products are used for creating the applications have influence on our testing too.
The definition of testing, for us, is the process of finding the most important bugs in a short period of time.
Can we use any test automation tools in exploratory testing?
There is a lot of good, bad, and sometimes difficult to use tools for software testers with a long pay back and learning period.
Many important small tools that we now need are missing. Let us take one example.
"Test Procedure Recorder" tool. This tool records our testing activities during the time that we are studying and testing an application using exploratory testing. All activities must be recorded in easy to read plain English, and may be in a simple, plain text format e.g. in notepad. There must be a possibility to correct records and make comments at any time. The objective is to have a soft copy of all our activities at any time. Sometimes we do not really need the complex replay function, because the automation of this test case is very difficult. We always need to have the possibility of reproducing our activities at any time. If we will find the bug, the record made by this tool will be the draft of the bug report and the directions to the developer how to reproduce it.
|
可不可不要这么样徘徊在目光内
你会察觉到我根本寂寞难耐
即使千多百个深夜曾在梦境内
我有吻过你这毕竟并没存在
人声车声开始消和逝
无声挣扎有个情感奴隶
是我多么的想她
但我偏偏只得无尽叹谓
其实每次见你我也着迷
无奈你我各有角色范围
就算在寂寞梦内超出好友关系
唯在暗里爱你暗里着迷
无谓要你惹上各种问题
共我道别吧别让空虚使我越轨
|
|
[楼 主]
|
Posted: 2005-11-30 09:27 |
| |
软件测试基地论坛 -> 英语天天看 -> Discussion about exploratory testing.
